ThreatPort Feature

Free Email Spoofing Test

Check whether an attacker can send email that appears to come from your domain. SPF, DKIM and DMARC in one pass.

Whether someone can send mail as your domain is a single question, but answering it needs three records read together. SPF authorises sending servers, DKIM signs the message, and DMARC tells receivers what to do when the first two fail — and it is DMARC that decides the outcome. A domain with perfect SPF and DKIM but DMARC at p=none is still spoofable, because p=none instructs receivers to deliver failing mail anyway.

  • DMARC at p=none: spoofing is reported but not blocked

  • No DMARC record, so receivers have no instruction at all

  • SPF present but ending in +all, authorising every sender

  • No DKIM signature, so forwarded mail cannot authenticate

  • How ThreatPort solves this

    ThreatPort reads all three records in one lookup and reports the outcome that actually matters: whether a forged message from your domain would be delivered, quarantined or rejected. Each record is shown with what it says, so the gap is visible rather than inferred.

    DMARC policy: none, quarantine or reject
    SPF record, lookup count and all mechanism
    DKIM selector probe at the common names
    MX records and TLS certificate in the same pass
    No signup, no email

    Frequently Asked Questions

    Can someone really send email as my domain?

    SMTP has no built-in way to verify the sender, so anyone can compose a message with your address in the From header. Whether it reaches an inbox depends on what your DMARC record instructs receivers to do. With no DMARC record, or DMARC at p=none, it is delivered.

    I have SPF and DKIM. Is that enough?

    Not on its own. SPF and DKIM give receivers a way to test a message, but DMARC is what tells them to act on a failed test. Without a DMARC policy of quarantine or reject, a receiver that detects a forgery is still free to deliver it.

    What is the difference between p=none, quarantine and reject?

    p=none asks receivers to report failures and change nothing, which is the right starting point while you find out what legitimate mail is failing. p=quarantine sends failing mail to spam. p=reject has the receiving server refuse it during the SMTP conversation, so it never reaches the recipient at all.

    Why do most domains stay at p=none?

    Because moving off it means finding every service that sends on the domain's behalf — billing, ticketing, marketing, monitoring — and getting each one authorised. That work is unglamorous and easy to defer, so the record is published, the reports go unread, and the domain stays spoofable while appearing protected.

    Does this test send an email?

    No. It reads the SPF, DKIM and DMARC records your domain publishes in DNS and reports what they instruct receivers to do. Nothing is sent to or from the domain.

    Start in minutes

    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