SurfaceMap › n › nyt.com

nyt.com

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

Domain & DNS

warn

26 passed 3 warn 0 failed

Areas

iRegistration ✓Delegation iNameservers !SOA !DNSSEC ✓Records

Problems

  • !
    Serials differ
    SOA · The nameservers serve different versions of the zone: 1 on ns-1328.awsdns-38.org (205.251.197.48), ns-1328.awsdns-38.org (2600:9000:5305:3000::1), ns-1652.awsdns-14.co.uk (205.251.198.116), ns-1652.awsdns-14.co.uk (2600:9000:5306:7400::1), ns-244.awsdns-30.com (205.251.192.244), ns-244.awsdns-30.com (2600:9000:5300:f400::1), ns-635.awsdns-15.net (205.251.194.123), ns-635.awsdns-15.net (2600:9000:5302:7b00::1); 1644596733 on dns1.p06.nsone.net (198.51.44.6), dns1.p06.nsone.net (2620:4d:4000:6259:7:6:0:1), dns2.p06.nsone.net (198.51.45.6), dns2.p06.nsone.net (2a00:edc0:6259:7:6::2), dns3.p06.nsone.net (198.51.44.70), dns3.p06.nsone.net (2620:4d:4000:6259:7:6:0:3), dns4.p06.nsone.net (198.51.45.70), dns4.p06.nsone.net (2a00:edc0:6259:7:6::4). This is normal for a few minutes after a change; if it lasts, zone transfers to the secondaries are failing.
    #22
  • !
    Unusual SOA timers
    SOA · refresh 5m is outside 20m–1d. Current values: refresh 5m, retry 2m30s, expire 14d, 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

Recent checks

!

Full report

Domain & DNS report for nyt.com ›

Mail

fail

23 passed 3 warn 1 failed

Areas

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

Problems

  • ✗
    No DKIM keys published
    DKIM · _domainkey.nyt.com does not exist (NXDOMAIN), so no DKIM keys are published. DKIM helps prevent email spoofing. Configure DKIM with your email service provider.
    #7
  • !
    Not enabled
    DNSSEC · DNSSEC is not enabled for this domain. Consider enabling DNSSEC to protect against DNS spoofing attacks.
    #8
  • !
    More than 5 MX records
    MX · Found 7 MX records, which is more than the recommended maximum of 5. Too many MX records may indicate a misconfiguration.
    #13
  • !
    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 nyt.com ›