SurfaceMap › m › mcmaster.com

mcmaster.com

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

Domain & DNS

warn

24 passed 5 warn 0 failed

Areas

iRegistration !Delegation !Nameservers !SOA !DNSSEC !Records

Problems

  • !
    NS sets differ
    Delegation · The nameservers at the parent and in the zone should be the same. Only at the parent: a1-3.akam.net, a20-66.akam.net, a5-67.akam.net, a6-64.akam.net, a8-65.akam.net, a9-66.akam.net, ns1-106.akam.net, ns1-203.akam.net, ns1-25.akam.net. a1-3.akam.net, a20-66.akam.net, a5-67.akam.net, a6-64.akam.net, a8-65.akam.net, a9-66.akam.net, ns1-106.akam.net, ns1-203.akam.net, ns1-25.akam.net, ns1.mcmaster.com, ns2.mcmaster.com, ns3.mcmaster.com, ns4.mcmaster.com report NS ns1.mcmaster.com ns2.mcmaster.com ns3.mcmaster.com ns4.mcmaster.com.
    #7
  • !
    Software version disclosed
    Nameservers · These nameservers report their software version via version.bind/version.server, which helps attackers find known vulnerabilities: a1-3.akam.net: "41824.4"; a1-3.akam.net: "41824.6"; a20-66.akam.net: "48878.33"; a20-66.akam.net: "48878.30"; a5-67.akam.net: "41824.7"; a5-67.akam.net: "41824.11"; a6-64.akam.net: "48878.30"; a6-64.akam.net: "48878.33"; a8-65.akam.net: "48878.27"; a9-66.akam.net: "41824.8"; a9-66.akam.net: "41824.11"; ns1-106.akam.net: "41824.7"; ns1-203.akam.net: "41824.7"; ns1-203.akam.net: "41824.6"; ns1-25.akam.net: "41824.9"; ns1-25.akam.net: "41824.6". Hide or replace the version string.
    #17
  • !
    Unusual SOA timers
    SOA · refresh 1m is outside 20m–1d; retry 15m should be shorter than refresh 1m; expire 1d is shorter than 7d; secondaries stop answering too soon when the primary is down; negative caching TTL (minimum) 1m is outside 5m–1d (RFC 2308 recommends 1–3 hours). Current values: refresh 1m, retry 15m, expire 1d, negative TTL 1m.
    #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 (1m), MX (1m), NS (1m). Low TTLs are useful just before a planned change. The NS TTL at the parent is 2d and in the zone 1m; resolvers may use either.
    #32

Recent checks

!

Full report

Domain & DNS report for mcmaster.com ›

Mail

fail

22 passed 4 warn 1 failed

Areas

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

Problems

  • ✗
    Policy: none (monitoring only)
    DMARC · DMARC policy is set to 'none', which only monitors but doesn't protect against spoofing. Consider upgrading to 'quarantine' or ideally 'reject'.
    #4
  • !
    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: mx0a-00570c01.pphosted.com, mx0b-00570c01.pphosted.com
    #11
  • !
    1024-bit DKIM key
    DKIM · 1024-bit RSA keys are the minimum and are considered weak today: s1 (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 mcmaster.com ›