SurfaceMap › p › paychex.com

paychex.com

Checked 2026-10-22 10:12 UTC · first added 2026-10-21
!Passed with warnings Score 73 of 100

Domain & DNS

warn

23 passed 4 warn 0 failed

Areas

iRegistration iDelegation !Nameservers !SOA !DNSSEC !Records

Problems

  • !
    Software version disclosed
    Nameservers · These nameservers report their software version via version.bind/version.server, which helps attackers find known vulnerabilities: a1-21.akam.net: "41824.8"; a12-65.akam.net: "48878.31"; a12-65.akam.net: "48878.32"; a16-64.akam.net: "48878.31"; a16-64.akam.net: "48878.27"; a2-64.akam.net: "48878.32"; a2-64.akam.net: "48878.26"; a7-66.akam.net: "41824.11"; a7-66.akam.net: "41824.4"; a9-64.akam.net: "41824.11"; a9-64.akam.net: "41824.9". Hide or replace the version string.
    #17
  • !
    Unusual SOA timers
    SOA · refresh 5m is outside 20m–1d. Current values: refresh 5m, retry 3m, expire 7d, negative TTL 5m.
    #23
  • !
    Not signed
    DNSSEC · The zone is not signed with DNSSEC, so answers can be spoofed. Enable DNSSEC at your DNS provider and publish the DS record at your registrar.
    #27
  • !
    Very low TTLs
    Records · These records have a TTL below 5m, causing extra queries and slower lookups: A (30s), NS (0s). Low TTLs are useful just before a planned change. The NS TTL at the parent is 2d and in the zone 0s; resolvers may use either.
    #32

Recent checks

!

Full report

Domain & DNS report for paychex.com ›

Mail

warn

24 passed 5 warn 0 failed

Areas

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

Problems

  • !
    Uses deprecated ptr mechanism
    SPF · The ptr mechanism in SPF records is deprecated due to performance issues and should be avoided.
    #1
  • !
    Not enabled
    DNSSEC · DNSSEC is not enabled for this domain. Consider enabling DNSSEC to protect against DNS spoofing attacks.
    #8
  • !
    Hosts without IPv6
    MX · The following MX hosts could not be resolved to IPv6 addresses: mxa-0018d001.gslb.pphosted.com, mxb-0018d001.gslb.pphosted.com
    #11
  • !
    1024-bit DKIM key
    DKIM · 1024-bit RSA keys are the minimum and are considered weak today: dkim (1024 bits), s2 (1024 bits). Rotate to a 2048-bit key.
    #23
  • !
    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 paychex.com ›