SurfaceMap › p › panix.com

panix.com

Checked 2026-10-22 10:11 UTC · first added 2026-10-21
✗Problems found Score 66 of 100

Domain & DNS

warn

26 passed 3 warn 0 failed

Areas

iRegistration !Delegation !Nameservers !SOA iDNSSEC ✓Records

Problems

  • !
    Nameservers in one network
    Delegation · all IPv4 addresses are in 198.7.0.0/24; all IPv6 addresses are in 2602:f977::/48. A single network failure takes all nameservers down; RFC 2182 recommends topologically separate networks (anycast setups are an exception).
    #10
  • !
    Software version disclosed
    Nameservers · These nameservers report their software version via version.bind/version.server, which helps attackers find known vulnerabilities: ns1.access.net: "9.20.24"; ns2.access.net: "9.20.24". Hide or replace the version string.
    #17
  • !
    Unusual SOA timers
    SOA · refresh 5m is outside 20m–1d; retry 5m should be shorter than refresh 5m. Current values: refresh 5m, retry 5m, expire 1000h, negative TTL 15m.
    #23

Recent checks

!

Full report

Domain & DNS report for panix.com ›

Mail

fail

20 passed 5 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
  • !
    Ends with ?all (neutral)
    SPF · SPF record uses ?all (neutral), which gives no protection against unauthorized senders. Use -all or ~all instead.
    #3
  • !
    No key under common selectors
    DKIM · The _domainkey name exists but no DKIM key was found under the common selectors. Selectors are provider-specific; check yours with -selector.
    #7
  • !
    Hosts without IPv6
    MX · The following MX hosts could not be resolved to IPv6 addresses: mx.panix.com
    #11
  • !
    Single MX host, no backup
    MX · Only one MX record found. For better email reliability, consider adding at least one backup MX server.
    #12
  • !
    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 panix.com ›