Pulls live X.509 certificate history from crt.sh and DNS/SPF/DMARC records from Google Public DNS — entirely in your browser.
Abaklabs Inspector runs three checks on any public domain, entirely in your browser: it looks up the domain's SSL/TLS certificate history through Certificate Transparency logs, checks whether the domain has a valid SPF record, and checks whether it has a DMARC policy configured. Together, SPF and DMARC are what stop attackers from sending phishing emails that appear to come from your domain — a missing or weak configuration is one of the most common gaps found in email security audits.
Enter your domain above and open the Email Spoofing Defense tab. It checks whether your domain publishes an SPF record (starting with v=spf1) and a DMARC record (starting with v=DMARC1) in DNS. If either is missing, it's meaningfully easier for someone to forge an email that looks like it came from your domain.
DMARC records have to be published as a TXT record at _dmarc.yourdomain.com, not at the bare domain. The most common issues are: no record at all, a typo in the v=DMARC1 tag, or a policy of p=none, which only monitors mail and doesn't actually block anything spoofed. This tool shows you the exact record it found and flags weak policies.
Without an SPF record, receiving mail servers have no list of which servers are allowed to send mail on your domain's behalf — so there's nothing stopping a phishing email from claiming to be from your domain.
Open the SSL/TLS Certificate Data tab after running a scan. It shows the current certificate's issuer, validity dates, a countdown to expiration, and the full history of publicly logged certificates pulled from Certificate Transparency logs via crt.sh.
Yes — it's free with no account or email address required. It runs client-side in your browser and queries two public APIs: Google Public DNS and crt.sh.
SPF lists which mail servers are authorized to send for a domain. DKIM adds a cryptographic signature to outgoing mail so receivers can verify it wasn't altered. DMARC ties the two together and tells receiving servers what to do — quarantine, reject, or do nothing — when a message fails both checks. This tool currently checks SPF and DMARC; DKIM validation requires knowing the specific selector used by your mail provider.