SurfaceMap › m › mercer.com

mercer.com

Checked 2026-10-22 09:50 UTC · first added 2026-10-21
✗Problems found Score 65 of 100

Domain & DNS

fail

27 passed 2 warn 1 failed

Areas

iRegistration !Delegation ✗Nameservers iSOA !DNSSEC iRecords

Problems

  • ✗
    No DNS over TCP
    Nameservers · DNS over TCP is required (RFC 7766); without it, large answers such as DNSSEC responses fail. Not answering over TCP: ns03.mmc.com (205.156.137.100): read tcp 46.225.38.91:53676->205.156.137.100:53: read: connection reset by peer.
    #19
  • !
    No IPv6
    Delegation · None of the nameservers has an IPv6 address, so IPv6-only resolvers can't reach them.
    #13
  • !
    NSEC3 with extra iterations or salt
    DNSSEC · NSEC3 uses 10 iterations and a 8-byte salt. RFC 9276 recommends 0 iterations and no salt: extra iterations cost resolvers CPU and add no real protection, and some validators treat high counts as insecure.
    #31

Recent checks

✗

Full report

Domain & DNS report for mercer.com ›

Mail

fail

27 passed 3 warn 1 failed

Areas

✓SPF ✓DMARC ✗DKIM !DNSSEC !MX !TLS iBIMI

Problems

  • ✗
    Weak DKIM key
    DKIM · RSA keys shorter than 1024 bits can be cracked and are ignored by receivers (RFC 8301): pm (768 bits). Rotate to a 2048-bit key.
    #23
  • !
    Hosts without IPv6
    MX · The following MX hosts could not be resolved to IPv6 addresses: mxa-001b7601.gslb.pphosted.com, mxb-001b7601.gslb.pphosted.com
    #11
  • !
    Signatures expire in 80h0m0s
    DNSSEC · DNSKEY signatures expire at 2026-10-25T17:42:27Z (in 80h0m0s). Check that re-signing works.
    #21
  • !
    Not configured
    TLS · 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

Recent checks

✗

Full report

Mail report for mercer.com ›