SurfaceMap › s › servicenow.com

servicenow.com

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

Domain & DNS

warn

29 passed 3 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-65.akam.net: "41824.4"; a1-65.akam.net: "41824.5"; a11-66.akam.net: "41824.6"; a11-66.akam.net: "41824.4"; a12-67.akam.net: "48878.31"; a13-64.akam.net: "41824.10"; a13-64.akam.net: "41824.11"; a24-65.akam.net: "48878.31"; a24-65.akam.net: "48878.30"; a26-66.akam.net: "48878.31"; a26-66.akam.net: "48878.26". Hide or replace the version string.
    #17
  • !
    Unusual SOA timers
    SOA · refresh 15m is outside 20m–1d; retry 30m should be shorter than refresh 15m; negative caching TTL (minimum) 1m is outside 5m–1d (RFC 2308 recommends 1–3 hours). Current values: refresh 15m, retry 30m, expire 365d, negative TTL 1m.
    #23
  • !
    Very low TTLs
    Records · These records have a TTL below 5m, causing extra queries and slower lookups: A (1m), MX (1m). Low TTLs are useful just before a planned change. The NS TTL at the parent is 2d and in the zone 5m; resolvers may use either.
    #32

Recent checks

!

Full report

Domain & DNS report for servicenow.com ›

Mail

warn

25 passed 4 warn 0 failed

Areas

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

Problems

  • !
    Hosts without IPv6
    MX · The following MX hosts could not be resolved to IPv6 addresses: us-smtp-inbound-1.mimecast.com, us-smtp-inbound-2.mimecast.com
    #11
  • !
    Signatures expire in 68h0m0s
    DNSSEC · DNSKEY signatures expire at 2026-10-25T06:34:06Z (in 68h0m0s). Check that re-signing works.
    #21
  • !
    1024-bit DKIM key
    DKIM · 1024-bit RSA keys are the minimum and are considered weak today: dkim (1024 bits), k1 (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 servicenow.com ›