SurfaceMap › p › phoenixcontact.com

phoenixcontact.com

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

Domain & DNS

warn

25 passed 4 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-61.akam.net, a10-64.akam.net, a11-65.akam.net, a22-66.akam.net, a4-67.akam.net, a5-64.akam.net; only in the zone: a1-73.akam.net, a10-66.akam.net, a11-67.akam.net, a12-64.akam.net, a16-65.akam.net, a3-66.akam.net. a1-61.akam.net, a1-73.akam.net, a10-64.akam.net, a10-66.akam.net, a11-65.akam.net, a11-67.akam.net, a12-64.akam.net, a16-65.akam.net, a22-66.akam.net, a3-66.akam.net, a4-67.akam.net, a5-64.akam.net report NS a1-73.akam.net a10-66.akam.net a11-67.akam.net a12-64.akam.net a16-65.akam.net a3-66.akam.net.
    #7
  • !
    Software version disclosed
    Nameservers · These nameservers report their software version via version.bind/version.server, which helps attackers find known vulnerabilities: a1-61.akam.net: "41824.9"; a1-61.akam.net: "41824.6"; a1-73.akam.net: "41824.6"; a1-73.akam.net: "41824.9"; a10-64.akam.net: "48878.33"; a10-66.akam.net: "48878.33"; a11-65.akam.net: "41824.5"; a11-65.akam.net: "41824.7"; a11-67.akam.net: "41824.8"; a11-67.akam.net: "41824.7"; a12-64.akam.net: "48878.33"; a12-64.akam.net: "48878.29"; a16-65.akam.net: "48878.30"; a16-65.akam.net: "48878.31"; a22-66.akam.net: "48878.29"; a3-66.akam.net: "41824.4"; a3-66.akam.net: "41824.11"; a4-67.akam.net: "48878.32"; a5-64.akam.net: "41824.8"; a5-64.akam.net: "41824.4". Hide or replace the version string.
    #17
  • !
    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 (20s). Low TTLs are useful just before a planned change. The NS TTL at the parent is 2d and in the zone 4h; resolvers may use either.
    #32

Recent checks

!

Full report

Domain & DNS report for phoenixcontact.com ›

Mail

warn

29 passed 3 warn 0 failed

Areas

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

Problems

  • !
    Not enabled
    DNSSEC · DNSSEC is not enabled for this domain. Consider enabling DNSSEC to protect against DNS spoofing attacks.
    #8
  • !
    Single MX host, no backup
    MX · Only one MX record found. For better email reliability, consider adding at least one backup MX server.
    #12
  • !
    1024-bit DKIM key
    DKIM · 1024-bit RSA keys are the minimum and are considered weak today: selector1 (1024 bits). Rotate to a 2048-bit key.
    #23

Recent checks

!

Full report

Mail report for phoenixcontact.com ›