🔒
HTTPS, TLS & redirects
Whether the site uses encryption, when the certificate was issued, and whether it silently redirects you elsewhere.
HTTPS is the padlock in your browser bar. It means traffic between you and the site is encrypted. Every legitimate site has it now; certificates are free. We also check when the certificate was issued (a brand-new one combined with other flags is suspicious) and whether the site is silently redirecting you to a different domain.
HTTPS alone isn’t a security guarantee. Scammers happily use it because it’s free. But the absence of HTTPS, especially on anything claiming to take payment or logins, is a hard fail. A very recently issued certificate on a domain claiming to be an established retailer is suspicious. A redirect that takes you from “nike-uk.shop” to a totally different domain is a major flag.
We flag missing or broken HTTPS, recently issued certificates, absent security headers, and redirects to a different domain than the one you typed.
Signals you might see
HTTPS activeNo HTTPSRedirects to different domainTLS handshake failedVery recent TLS certificateRecent TLS certificateMissing security headers
🛰️
Infrastructure signals
What’s behind the domain, its hosting and nameservers, and whether they look real or disposable.
Every site lives on some hosting infrastructure. We look at the nameservers (who runs the DNS), the IP addresses (where the site is actually served), and the network they’re on. Some patterns are dead giveaways, like domains parked on registrar default nameservers, sites served from anonymizing networks, or domains with no resolvable web hosting at all.
Real businesses host on real services such as Cloudflare, AWS, Shopify, and GoDaddy hosting. Scams often use anonymized networks or simply don’t have proper hosting set up because their lifespan is days. This is back-end signal that’s hard to spoof.
We flag parking-oriented nameservers (the domain isn’t actively hosted), no web-host IP records (nothing serves a website at this domain), and anonymized hosting networks with poor abuse-handling reputations.
Signals you might see
Parking-oriented nameserversNo web host IP recordsAnonymized hosting network
📧
Email & business setup
Whether the domain is set up to send and receive email like a real business, or has none of the usual infrastructure.
Real businesses configure email. They set up MX records (where mail is delivered), SPF or DMARC records (so their messages don't get marked as spam), and so on. Throwaway scam domains usually skip all of this. They're built to host one page for a few days, not run a business.
It's not a slam-dunk on its own. Some legitimate hobby sites and static landing pages have minimal email setup. But if a domain claims to be an established retailer and can't receive customer emails, something's off.
We flag domains with no MX records, no SPF or DMARC, or a setup that exists only as a defensive measure with no real mail server behind it.
Signals you might see
Email records configuredNo email infrastructureNo mail recordsFree webmail contact
🚩
Domain pattern
Telltale signs in the domain’s structure: sketchy extensions, too many hyphens, suspicious words.
Beyond impersonation, certain patterns in a domain itself suggest fraud. Some top-level domains (.zip, .top, .xyz, .tk) are heavily abused by scammers because they’re cheap, fast to register, and often unmoderated. Multi-hyphen names like “secure-login-verify-account.com” are vanishingly rare on legitimate sites. URL paths containing words like “verify-now” or “update-payment” almost never appear on real businesses.
These patterns aren’t proof on their own. There are perfectly legitimate sites on .xyz, and some businesses use hyphens, but they shift the prior. Combined with other flags, they tilt the verdict.
We flag sketchy TLDs from known abuse lists, domains with excessive hyphens, unusually long domains, phishing-keyword paths and queries, and suspicious structural prefixes.
Signals you might see
Sketchy TLDHyphen overloadVery long domainPhishing keywordSuspicious domain prefixSuspicious URL path patternSensitive query parametersEncoded redirect pattern
🎭
Brand impersonation
Domains designed to look like a known brand by tweaking spelling or using lookalike characters.
Scammers try to pass off their domain as a brand you trust. The classic moves are swapping a number for a letter (paypa1.com instead of paypal.com), padding with plausible words (nike-store-uk.shop), or using characters from another alphabet that look identical. An “a” from Cyrillic instead of Latin reads the same to your eyes but is technically a different domain.
If you’re skim-reading a URL in an SMS or email, a clever lookalike will sail past you. This is how phishing kits steal millions from people who would never knowingly hand credentials to a fake.
We flag number-for-letter swaps on big-brand names, padded-out domains that mash a brand into a long string, and mixed-script domains where Cyrillic, Greek, or other characters substitute for Latin ones.
Signals you might see
Brand impersonationBrand-associated domainLikely brand typosquatNumber-for-letter swapMixed-script lookalikeBrand favicon impersonation