SurfaceMap › p › pagerduty.com

pagerduty.com

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

Domain & DNS

warn

29 passed 2 warn 0 failed

Areas

iRegistration iDelegation ✓Nameservers !SOA ✓DNSSEC !Records

Problems

  • !
    Unusual SOA timers
    SOA · negative caching TTL (minimum) 1m is outside 5m–1d (RFC 2308 recommends 1–3 hours). Current values: refresh 2h, retry 15m, expire 14d, negative TTL 1m.
    #23
  • !
    Very low TTLs
    Records · These records have a TTL below 5m, causing extra queries and slower lookups: A (1m), MX (30s). Low TTLs are useful just before a planned change.
    #32

Recent checks

!

Full report

Domain & DNS report for pagerduty.com ›

Mail

fail

29 passed 2 warn 1 failed

Areas

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

Problems

  • ✗
    Policy not reachable
    TLS · The MTA-STS record exists but the policy could not be fetched, so senders ignore MTA-STS: https://mta-sts.pagerduty.com/.well-known/mta-sts.txt returned HTTP 404.
    #33
  • !
    Signatures expire in 8h0m0s
    DNSSEC · DNSKEY signatures expire at 2026-10-22T18:00:00Z (in 8h0m0s). Check that re-signing works.
    #21
  • !
    1024-bit DKIM key
    DKIM · 1024-bit RSA keys are the minimum and are considered weak today: s2 (1024 bits). Rotate to a 2048-bit key.
    #23

Recent checks

✗

Full report

Mail report for pagerduty.com ›