Google Safe Browsing
PassNo threats found by Google Safe Browsing.
Weight 22Contribution +22 / 22
Learn more
Google's threat database flags sites known to host malware, phishing, or unwanted software. A clean result is a strong positive signal.
Domain Safety Report
example.com
Likely SafeConfidence
80%
TrustDepth Score™
83/100
83
example.com looks safe overall. It uses HTTPS correctly, has existed for over 30 years, is not on Google's phishing or malware lists, and publishes SPF and DMARC email records. However, it does not publish contact, about, or privacy pages.
Security Verification Log
Algorithm v2
Why this score?
This website scored 83/100 because:
- No threats found by Google Safe Browsing.
- Registered 30 years ago · via RESERVED-Internet Assigned Numbers Authority.
- Valid HTTPS certificate.
- SPF ✓ DMARC ✓ DNSSEC ✓
- Reachable over HTTPS.
- No suspicious naming patterns.
- No redirects.
- No standard security headers set.
- No contact, about, privacy or terms links found on the homepage.
- server: cloudflare
HTTPS EnabledDNSSEC EnabledSPF FoundDMARC FoundEstablished (10+ yrs)No Contact/Privacy
Verified by TrustDepthChecked Scan ID
TD-297324Scan took 4140 msTrust Statistics
- TrustDepth Score
- 83/ 100
- Confidence
- 80%
- Domain Age
- 30y
- Blocklists
- —
- Security Checks
- 7 / 12Passed
- Last Scan
- 8 days ago
Data sourcesRDAP (WHOIS)Cloudflare DNSGoogle Safe BrowsingURLhausLive reachabilityTLS probe
example.com at a glance
How this domain connects to the rest of the TrustDepth graph.
- Category
- Other
- Registrar
- RESERVED-Internet Assigned Numbers Authority
- Age
- 30 years
Score breakdown
Every signal, its weight, and how many points it contributed to example.com's score.
Abuse blocklists
UnknownNot available — provider did not respond.
Weight 18Contribution +13 / 18
Learn more
We check independent abuse databases like URLhaus and PhishTank. Being listed means researchers have observed the site being used maliciously.
Domain age (WHOIS)
PassRegistered 30 years ago · via RESERVED-Internet Assigned Numbers Authority.
Weight 13Contribution +13 / 13
Learn more
Older domains are much less likely to be scams. Most phishing sites are registered within the last 90 days.
SSL / TLS certificate
PassValid HTTPS certificate.
Weight 8Contribution +8 / 8
Learn more
A valid HTTPS certificate proves the site owns the domain and encrypts traffic. Broken or missing certificates are a red flag.
DNS configuration
PassSPF ✓ DMARC ✓ DNSSEC ✓
Weight 8Contribution +8 / 8
Learn more
SPF, DMARC and DNSSEC records help stop attackers from spoofing this domain in email or redirecting visitors to fake copies.
Reachability & HTTPS
PassReachable over HTTPS.
Weight 6Contribution +4 / 6
Learn more
We confirm the site actually responds, upgrades HTTP to HTTPS, and returns a healthy status code.
Naming & impersonation
PassNo suspicious naming patterns.
Weight 6Contribution +6 / 6
Learn more
Lookalike names, homoglyphs, brand-typosquats, suspicious TLDs, and digit-heavy strings correlate with scam sites.
Security headers
FailNo standard security headers set.
Weight 6Contribution +0 / 6
Learn more
HSTS, CSP, X-Frame-Options and Referrer-Policy show the operator takes basic browser-side hardening seriously.
Transparency pages
FailNo contact, about, privacy or terms links found on the homepage.
Weight 6Contribution +0 / 6
Learn more
Real businesses publish contact, about, privacy and terms pages. Missing all of them is a common scam pattern.
Redirect chain
PassNo redirects.
Weight 3Contribution +3 / 3
Learn more
Long redirect chains or cross-domain hops are common in cloaking, affiliate abuse, and phishing landers.
Tech fingerprint
Warningserver: cloudflare
Weight 2Contribution +1 / 2
Learn more
Robots.txt, sitemap.xml, server headers and framework markers show the site is a properly built, maintained web app.
Community reviews
UnknownNot available — provider did not respond.
Weight 2Contribution +1 / 2
Learn more
Signed-in visitors can share first-hand experiences. Aggregated ratings supplement automated checks.
Staying safe on example.com
Simple habits that keep you safe whether or not this site scores well.
Verify the URL character by character
Typosquats swap letters (rn for m, 0 for o). If in doubt, type the address instead of clicking a link.
Use a password manager
It only autofills on the exact domain — a great built-in phishing detector.
Prefer buyer-protected payments
Credit cards and PayPal Goods & Services let you dispute fraudulent charges. Wire and crypto do not.
Cross-check reviews independently
Search '<site> review' plus '<site> scam' to see the balance of opinions before trusting a new site.
Frequently asked about example.com
Is example.com a scam?+
Automated safety signals do not indicate example.com is a scam. That said, no automated system catches every fraud — always verify unusual offers independently.
Is example.com legit?+
example.com passes TrustDepth's core safety checks and is not present on any abuse blocklists we consult. It's likely legitimate.
Can I trust example.com?+
Most signals look good for example.com. Trust it for normal browsing, but be cautious with payment info.
Is example.com safe to use?+
example.com looks safe for everyday use based on our automated checks. Still practice basic hygiene: verify URLs, use strong unique passwords, and enable two-factor authentication.
How is example.com's safety score calculated?+
We combine live SSL, WHOIS, DNS and reachability checks with lookups against Google Safe Browsing and abuse blocklists such as URLhaus and PhishTank. Naming heuristics and (soon) community reviews add extra context. Each signal contributes a weighted portion of a 0–100 score.
Does example.com use a secure HTTPS connection?+
Our SSL/TLS check inspects the live certificate served by example.com, verifying issuer, validity window and hostname match. See the "SSL / TLS certificate" signal above for the exact result for this scan.
Has example.com been reported for phishing or malware?+
We cross-check example.com against Google Safe Browsing, URLhaus and PhishTank. If any of them flag the domain, it will show as a red signal in the "Safety signals" section above.
How old is the example.com domain?+
WHOIS registration age is one of the strongest anti-scam signals — most fraudulent sites are less than 90 days old. Check the "Domain age (WHOIS)" signal above for the registration date and age for example.com.
What should I do if example.com looks suspicious?+
Close the tab, do not enter any credentials, and do not download files. Report the URL to Google Safe Browsing (safebrowsing.google.com/safebrowsing/report_phish/) and to your browser's built-in reporting tool. If you already entered a password, change it immediately on the real site and enable 2FA.
How often is this example.com report updated?+
Every scan is live — signals are re-checked from source when you load this page (with a short cache to avoid rate limits). You can force a fresh scan any time by re-submitting example.com from the home page.
About this example.com safety report
TrustDepth generated this scorecard for example.com by running seven independent checks in parallel: SSL/TLS certificate validity, WHOIS registration age, DNS configuration (SPF, DMARC, DNSSEC), HTTPS reachability, Google Safe Browsing status, abuse blocklists (URLhaus, PhishTank), and naming heuristics. Each signal contributes a weighted share of the 0–100 score.
A verdict of trusted means the domain passed all core checks with high confidence. Likely safe means most signals are positive with one minor gap. Unclear means we don't have enough evidence to recommend for or against. Suspicious and dangerous mean at least one strong red flag — proceed with caution or avoid entirely.
Automated scans catch most fraud, but no scanner is perfect. Always cross-check unusual offers, verify contact details, and prefer payment methods with buyer protection. Read our methodology for the full scoring breakdown.
Community reports for example.com
Real reports from people who have used example.com. Add yours to help others decide.
Loading comments…