verisign.com

Checked 22 October 2026, 11:21 UTC · via 8.8.8.8
!Passed with warnings
23 passed 5 warnings 0 failed 3 info

SPF

pass

SPF record published

Found

Record
v=spf1 include:spf-i.verisign.com include:spf-p.verisign.com ~all
DNS lookups
10 of 10
Void lookups
0 of 2

Checks

  • ✓ No deprecated ptr mechanism #1
    No ptr mechanism found in SPF record.
  • ✓ 10 of 10 DNS lookups #2
    SPF record needs 10 DNS lookups (limit is 10).
  • ✓ Ends with ~all #3
    SPF record properly uses ~all to restrict unauthorized senders.
  • ✓ Record published #6
    SPF record exists for this domain.
  • ✓ Single record #16
    Exactly one SPF record is published.
  • ✓ Valid syntax #25
    All SPF mechanisms and modifiers are valid.
  • ✓ No void lookups #26
    All include/redirect targets exist.
  • ✓ No overly broad IP ranges #27
    All ip4/ip6 ranges are narrow enough.

DMARC

warn

p=quarantine (_dmarc.verisign.com)

Found

Record
v=DMARC1; p=quarantine; pct=100; rua=mailto:verisign@rua.agari.com,mailto:mailreports@verisign.com!10m; ruf=mailto:verisign@ruf.agari.com,mailto:mailauthfail@verisign.com!10m; rf=afrf; ri=86400
Found at
_dmarc.verisign.com
External report address
mailto:verisign@rua.agari.com (authorized)
External report address
mailto:verisign@ruf.agari.com (authorized)
TagValueMeaning
vDMARC1Version
pquarantinePolicy
pct100Percentage of mail the policy applies to
ruamailto:verisign@rua.agari.com,mailto:mailreports@verisign.com!10mAggregate report addresses
rufmailto:verisign@ruf.agari.com,mailto:mailauthfail@verisign.com!10mFailure report addresses
rfafrfFailure report format
ri86400Report interval (seconds)

Checks

  • !
    Policy: quarantine
    DMARC policy is set to 'quarantine'. Consider upgrading to 'reject' for stronger protection once you've verified legitimate emails are passing authentication.
    #4
  • ✓ Record published #5
    DMARC record exists for this domain.
  • ✓ Valid syntax #17
    DMARC record syntax is valid.
  • ✓ Applies to 100% of mail #18
    DMARC policy applies to all failing mail.
  • ✓ Aggregate reports enabled #19
    Aggregate reports are sent to: mailto:verisign@rua.agari.com, mailto:mailreports@verisign.com!10m
  • ✓ Subdomain policy: quarantine #20
    Subdomains are covered by policy 'quarantine'.
  • ✓ External report addresses authorized #29
    Report addresses in other domains have published their authorization.

DKIM

warn

No keys found under the checked selectors

Found

Selectors
None found
_domainkey
NOERROR

Checks

  • !
    No key under common selectors
    The _domainkey name exists but no DKIM key was found under the common selectors. Selectors are provider-specific; check yours with -selector.
    #7

DNSSEC

pass

Signed, DS published at parent

Found

DNSKEY records
Yes (2)
DS at parent
Yes
Algorithms
RSASHA256 (8)
Key tags
55204, 30594
Signatures valid until
20 November 2026, 23:19 UTC

Checks

  • ✓ Signed, DS published at parent #8
    DNSSEC is enabled for this domain (DNSKEY and DS present), providing additional security for DNS lookups.
  • ✓ Signatures valid until 2026-11-20 #21
    DNSKEY signatures are valid until 2026-11-20T23:19:26Z.

MX

warn

6 mail servers

Found

PriorityHostRecordsReverse DNS
10mail1.verisign.comA 72.13.63.30mail1.verisign.com ✓
10mail2.verisign.comA 72.13.63.31mail2.verisign.com ✓
10mail3.verisign.comA 72.13.63.32mail3.verisign.com ✓
10mail4.verisign.comA 69.58.187.30mail4.verisign.com ✓
10mail5.verisign.comA 69.58.187.31mail5.verisign.com ✓
10mail6.verisign.comA 69.58.187.32mail6.verisign.com ✓

Checks

  • ✓ 6 MX records #9
    Found 6 MX records for this domain.
  • ✓ All hosts resolve #10
    All MX records resolve to valid IP addresses.
  • !
    Hosts without IPv6
    The following MX hosts could not be resolved to IPv6 addresses: mail1.verisign.com, mail2.verisign.com, mail3.verisign.com, mail4.verisign.com, mail5.verisign.com, mail6.verisign.com
    #11
  • ✓ Redundant MX hosts #12
    Found 6 MX records, which provides redundancy for email delivery.
  • !
    More than 5 MX records
    Found 6 MX records, which is more than the recommended maximum of 5. Too many MX records may indicate a misconfiguration.
    #13
  • ✓ No localhost targets #14
    No MX records pointing to localhost found.
  • ✓ No private IP addresses #15
    No MX records resolving to private IP addresses found.
  • ✓ No CNAME targets #22
    No MX records point to a CNAME.
  • ✓ Reverse DNS confirmed #30
    All 6 MX addresss have a PTR record that resolves back to them.

TLS

warn

no MTA-STS · no TLS-RPT · DANE on 0 of 6 MX hosts

Found

DANE (TLSA records)

MX hostTLSADNSSEC
mail1.verisign.comnone-
mail2.verisign.comnone-
mail3.verisign.comnone-
mail4.verisign.comnone-
mail5.verisign.comnone-
mail6.verisign.comnone-

Checks

  • !
    Not configured
    MTA-STS is not configured, so other mail servers fall back to unencrypted delivery when TLS fails or is stripped by an attacker. Publish a _mta-sts TXT record and a policy at https://mta-sts.<domain>/.well-known/mta-sts.txt.
    #32
  • i
    Not configured
    TLS-RPT lets senders report TLS delivery problems to you. It is most useful together with MTA-STS or DANE.
    #35
  • i
    Not used
    No MX host publishes TLSA records. DANE lets senders verify your mail server's certificate through DNSSEC; it requires DNSSEC on the MX host's zone.
    #36

BIMI

info

No BIMI record

Checks

  • i
    Not configured
    BIMI shows your logo next to your mail in supporting mail clients. It requires DMARC enforcement.
    #38