SurfaceMap › p › puppet.com

puppet.com

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

Domain & DNS

warn

24 passed 3 warn 0 failed

Areas

iRegistration iDelegation ✓Nameservers !SOA !DNSSEC !Records

Problems

  • !
    Unusual SOA timers
    SOA · expire 3d is shorter than 7d; secondaries stop answering too soon when the primary is down. Current values: refresh 6h, retry 1h, expire 3d, negative TTL 5m.
    #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: MX (1s). Low TTLs are useful just before a planned change. The NS TTL at the parent is 2d and in the zone 6h; resolvers may use either.
    #32

Recent checks

!

Full report

Domain & DNS report for puppet.com ›

Mail

fail

27 passed 3 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: Get "https://mta-sts.puppet.com/.well-known/mta-sts.txt": http: server gave HTTP response to HTTPS client.
    #33
  • !
    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: s2 (1024 bits). Rotate to a 2048-bit key.
    #23

Recent checks

✗

Full report

Mail report for puppet.com ›