SurfaceMap › w › waitbutwhy.com

waitbutwhy.com

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

Domain & DNS

warn

28 passed 1 warn 0 failed

Areas

iRegistration iDelegation !Nameservers ✓SOA iDNSSEC iRecords

Problems

  • !
    Software version disclosed
    Nameservers · These nameservers report their software version via version.bind/version.server, which helps attackers find known vulnerabilities: eric.ns.cloudflare.com: "2026.10.2"; gene.ns.cloudflare.com: "2026.10.2". Hide or replace the version string.
    #17

Recent checks

!

Full report

Domain & DNS report for waitbutwhy.com ›

Mail

fail

24 passed 3 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
  • !
    1024-bit DKIM key
    DKIM · 1024-bit RSA keys are the minimum and are considered weak today: k1 (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 waitbutwhy.com ›