Check your SPF record, its lookup count and its all mechanism. No account, no email required.
SPF fails quietly. A record that exceeds ten DNS lookups returns permerror and stops protecting the domain, and a record ending in +all authorises every sender on the internet. Neither produces a bounce or a warning — mail keeps flowing and the domain keeps being spoofable.
More than ten DNS lookups — the record returns permerror and is ignored
A record ending in +all, which authorises any sender
A sending service added to the platform but never added to SPF
No SPF record at all, leaving receivers with nothing to check against
Enter a domain and ThreatPort reads its SPF record straight from public DNS, counts the include and redirect lookups it triggers, and reports the all mechanism it terminates with. The same check runs continuously on domains you verify, so a record that breaks after a vendor change is caught rather than discovered during an incident.
RFC 7208 caps an SPF evaluation at ten DNS lookups. Each include, a, mx, ptr, exists and redirect counts. Past ten, a conforming receiver returns permerror and treats the record as though it were not there, which means the domain is unprotected while still appearing to have SPF configured.
No. SPF authorises sending servers for the envelope sender, not the From header a recipient sees, so a message can pass SPF and still display someone else's address. Stopping visible spoofing needs DMARC at p=quarantine or p=reject, with SPF or DKIM aligned to the From domain.
Neither is universally right. -all tells receivers to reject anything from an unlisted server, which is stronger but breaks legitimate mail if a sending service is missing from the record. ~all marks it as suspicious instead. Most domains move to ~all first, confirm through DMARC reports that nothing legitimate is failing, then tighten to -all.
No. The SPF, DMARC, DKIM, MX and TLS checks run on any domain without signing up, because all of them read records the domain owner published in public DNS. An account is needed for the parts that are specific to infrastructure you own: the subdomain inventory, open ports, and continuous monitoring.
Yes for these checks, because they read published DNS. What requires verifying the domain on your account is the rest — resolved IPs, open ports, the services behind them, and vulnerability matching. Those are about a specific organisation's exposure and we do not hand them to anonymous callers.
No agents. No configuration. No professional services.
$50 per domain per month — cancel anytime.
Compared to enterprise ASM platforms that require a sales call for pricing.
We use essential cookies to operate this site and optional analytics cookies to improve it. Cookie Policy