SurfaceMap › u › usanetwork.com

usanetwork.com

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

Domain & DNS

warn

22 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: asia2.akam.net, asia3.akam.net, aus1.akam.net, eur3.akam.net, eur4.akam.net, ns1-102.akam.net, ns1-161.akam.net, use3.akam.net, usw1.akam.net; only in the zone: pdns129.ultradns.biz, pdns129.ultradns.com, pdns129.ultradns.net, pdns129.ultradns.org. asia2.akam.net, asia3.akam.net, aus1.akam.net, eur3.akam.net, eur4.akam.net, ns1-102.akam.net, ns1-161.akam.net, pdns129.ultradns.biz, pdns129.ultradns.com, pdns129.ultradns.net, pdns129.ultradns.org, use3.akam.net, usw1.akam.net report NS pdns129.ultradns.biz pdns129.ultradns.com pdns129.ultradns.net pdns129.ultradns.org.
    #7
  • !
    Software version disclosed
    Nameservers · These nameservers report their software version via version.bind/version.server, which helps attackers find known vulnerabilities: asia2.akam.net: "48878.32"; asia3.akam.net: "48878.26"; aus1.akam.net: "41824.4"; eur3.akam.net: "48878.32"; eur4.akam.net: "41824.7"; ns1-102.akam.net: "41824.10"; ns1-102.akam.net: "41824.6"; ns1-161.akam.net: "41824.7"; ns1-161.akam.net: "41824.10"; use3.akam.net: "41824.4"; usw1.akam.net: "41824.7". Hide or replace the version string.
    #17
  • !
    Unusual SOA timers
    SOA · refresh 15m is outside 20m–1d; retry 1h should be shorter than refresh 15m. Current values: refresh 15m, retry 1h, expire 30d, negative TTL 15m.
    #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 (20s), AAAA (20s). Low TTLs are useful just before a planned change. The NS TTL at the parent is 2d and in the zone 1d; resolvers may use either.
    #32

Recent checks

!

Full report

Domain & DNS report for usanetwork.com ›

Mail

fail

20 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
  • !
    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
  • !
    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-00a17301.gslb.pphosted.com, mxb-00a17301.gslb.pphosted.com, mx0a-00a17301.pphosted.com, mx0b-00a17301.pphosted.com
    #11
  • !
    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 usanetwork.com ›