Fraud verification

How to Detect Fraudulent Domains

Fraudulent domains share a small set of operational fingerprints: very young WHOIS records, mismatched DNS, fresh free SSL certificates, and clean-by-newness reputation scores. Here's how to spot them.

Quick summary

  • Domain age under 90 days is the strongest single signal.
  • Free SSL means nothing about operator identity.
  • Lookalike characters belong in your verification checklist.
  • Combine signals — no single check decides a verdict.

The fraud fingerprint

  • Age — registered days or weeks ago.
  • WHOIS — privacy-shielded with no business identity.
  • DNS — minimal records, missing MX, no real mail infrastructure.
  • SSL — Let's Encrypt cert issued in the last 24 hours.
  • Lookalike — homoglyph or near-match to a known brand.
  • Reputation — clean only because no one's reported it yet.

How investigators chain the signals

No single check is conclusive — a legitimate startup can also be under 90 days old. Combine age + DNS hygiene + certificate freshness + lookalike pattern. Three matching signals is a strong verdict.

Troubleshooting workflow

Run through these steps in order. Each step links to the right diagnostic tool.

  1. 1

    Check domain age

    WHOIS / RDAP creation date is the first thing to look at.

    Open Domain Age
  2. 2

    Inspect DNS hygiene

    Real businesses have MX, SPF, and consistent A/AAAA records.

    Open DNS Lookup
  3. 3

    Inspect the certificate

    Note the issuer and the not-before date.

    Open SSL Checker
  4. 4

    Pull reputation

    Cross-check IP and domain reputation feeds.

    Open Domain Reputation

Frequently asked questions

What's the single strongest fraud signal?

Domain age. The vast majority of phishing and scam domains are under 90 days old when used.

Why isn't a valid SSL certificate enough?

Free certificates are issued in seconds with no identity verification. SSL proves the connection is encrypted, not that the operator is legitimate.

Are blacklists reliable for fresh fraud?

Reactive blacklists lag the first wave of abuse. Use age, DNS hygiene, and SSL freshness together — they catch fraud the reactive feeds haven't seen yet.

How do I automate this for inbound links?

Save the verification sequence as a workflow and resume it on any suspicious URL or domain. Mature teams run it from a saved monitoring workspace.

Monitor it continuously

Save this check, get alerts on changes, and track multiple domains in one dashboard.

Learn about monitoring