SurfaceMap › s › stanforddaily.com

stanforddaily.com

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

Domain & DNS

warn

29 passed 1 warn 0 failed

Areas

iRegistration iDelegation !Nameservers ✓SOA iDNSSEC ✓Records

Problems

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

Recent checks

!

Full report

Domain & DNS report for stanforddaily.com ›

Mail

fail

22 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
  • !
    1 of 10 DNS lookups, with problems
    SPF · SPF record needs 1 DNS lookups (limit is 10). Problems found: include:mailgun.org could not be resolved: DNS query for mailgun.org failed: read udp 46.225.38.91:53864->8.8.8.8:53: i/o timeout.
    #2
  • !
    No aggregate reports (rua)
    DMARC · DMARC record has no rua tag, so you receive no aggregate reports about who sends mail as your domain. Add rua=mailto:...
    #19
  • !
    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 stanforddaily.com ›