Security Report for example.com
Quick Answer
This domain already shows strong risk signals. Stop interacting, preserve the page, chat, phone, and payment evidence, and move into response or reporting immediately.
Positive Signals
- + Domain has been active for 30 years
- + Google Safe Browsing: Safe
- + Valid SSL certificate
- + HTTPS encryption supported
- + DNSSEC enabled
Concerns
- - 4 security sources flagged as suspicious
Score Breakdown
Was this assessment accurate?
Advanced Scan
Comprehensive data lookup across premium sources
- Website history verification
- Detailed WHOIS information
- Reverse WHOIS association
- Traffic rank analysis
- Company registration check
AI Deep Investigation
Cross-check the story, claims, and supporting evidence before you decide
- Everything in Advanced Scan
- AI website content analysis
- AI cross-reference verification
- Claim authenticity validation
- Detailed report with evidence
Comprehensive Investigation
Full-spectrum investigation with company deep search & social intelligence
- Everything in Deep Investigation
- AI company background search
- Social media intelligence
- Detailed suspicious point analysis
- Event timeline & entity connections
This analysis is for informational purposes only and does not constitute a legal determination.
Security Sources
Domain Information
- Registrar
- RESERVED-Internet Assigned Numbers Authority
- Created
- August 14, 1995
- Expires
- August 13, 2026
- Domain Age
- 30 years
- DNSSEC
- Enabled
- Nameservers
- ELLIOTT.NS.CLOUDFLARE.COM, HERA.NS.CLOUDFLARE.COM
- Domain Status
- client delete prohibited client transfer prohibited client update prohibited
SSL/TLS Certificate
- Issuer
- C=GB, O=Sectigo Limited, CN=Sectigo Public Server Authentication CA DV E36
- Valid From
- February 14, 2026
- Valid To
- May 15, 2026
- Status
- Valid
Server Information
- IP Address
- 104.18.26.120
- Hosting Provider
- Cloudflare, Inc.
- ASN
- AS13335 Cloudflare, Inc.
- Server Location
- Toronto, Canada
- Organization
- Cloudflare, Inc.
Related Intelligence
Technical Details (DNS / Headers / Subdomains)
DNS Records
Email Security
SPF Configured DMARC Configured| Type | Value |
|---|---|
| A | 104.18.26.120 |
| A | 104.18.27.120 |
| AAAA | 2606:4700::6812:1b78 |
| AAAA | 2606:4700::6812:1a78 |
| MX | 0 |
| NS | hera.ns.cloudflare.com |
| NS | elliott.ns.cloudflare.com |
| TXT | v=spf1 -all |
| TXT | _k2n1y4vw3qtb4skdx9e7dxt97qrmmq9 |
HTTP Security Headers
0/6Channels / Subdomains
5 subdomains found| Subdomain | Title |
|---|---|
| www.example.com | Example Domain |
| m.example.com | - |
| dev.example.com | - |
| products.example.com | - |
| support.example.com | - |
Community Reports
Log in to report and share your experience
Report & Take Down This Website
High-Risk Signals
The risk signals are strong enough. Move on evidence preservation, reporting, and victim response now
This result is no longer just a normal verification case. Moving the chat, phone, payment, and official-reporting path in parallel is usually more important than waiting for more data.
Recommended First
Move into the victim action plan
If you already paid, logged in, or installed tools, use the action plan first to prioritize containment and evidence work.
Move into the website-reporting flow
Move the site, payment evidence, chat trail, and contact points into the formal reporting path.
Add the chat, DM, and payment-pressure trail
Keep the Telegram, WhatsApp, social DM, and payment-pressure trail in the same timeline.
Check the callback number and SMS
If the actor also used calls, SMS, or one-time codes, verify that phone path next.
The results are based on multiple third-party data sources and AI models. False positives or negatives may occur. This report should not be used as the sole basis for any decision. Please verify with additional sources.
If a loss already happened, move into the response flow now
Delay is the main risk with high-risk domains. Prioritize freezes, credential resets, reporting, and evidence preservation now.
If no loss happened yet, continue with the website-reporting and official-agency paths next.
FAQ
Is example.com safe to visit?
The current score is 56. Results like this are no longer watch-and-wait cases. Reporting, official complaints, and victim response should usually move in parallel.
Who owns example.com?
example.com is registered by RESERVED-Internet Assigned Numbers Authority, created on August 14, 1995.
What is example.com's SSL certificate?
example.com's SSL certificate is issued by C=GB, O=Sectigo Limited, CN=Sectigo Public Server Authentication CA DV E36, valid until May 15, 2026.
Where is example.com's server located?
example.com is hosted in Toronto, Canada, served by Cloudflare, Inc..
Is this report useful?
Use this report to tell others to stop interacting now and move straight into containment, evidence preservation, and reporting.
Forward to your parents — they deserve to browse safely too.
Last analyzed: April 3, 2026