SurfaceMap › t › today.com

today.com

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

Domain & DNS

warn

22 passed 5 warn 0 failed

Areas

iRegistration !Delegation !Nameservers !SOA !DNSSEC !Records

Problems

  • !
    No IPv6
    Delegation · None of the nameservers has an IPv6 address, so IPv6-only resolvers can't reach them.
    #13
  • !
    Software version disclosed
    Nameservers · These nameservers report their software version via version.bind/version.server, which helps attackers find known vulnerabilities: nsa1.today.com: "9.18.28"; nsa2.today.com: "9.18.28"; nsa3.today.com: "9.18.28"; nsa4.today.com: "9.18.28"; nsa5.today.com: "9.18.28"; nsa6.today.com: "9.18.28". Hide or replace the version string.
    #17
  • !
    Serials differ
    SOA · The nameservers serve different versions of the zone: 2026102253 on nsa3.today.com (13.52.111.184); 2026102275 on nsa1.today.com (54.200.82.65), nsa2.today.com (54.208.199.200), nsa4.today.com (18.191.2.199), nsa5.today.com (52.88.170.187), nsa6.today.com (34.228.98.149). This is normal for a few minutes after a change; if it lasts, zone transfers to the secondaries are failing.
    #22
  • !
    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: A (3m), MX (1m39s). Low TTLs are useful just before a planned change. The NS TTL at the parent is 2d and in the zone 5m; resolvers may use either.
    #32

Recent checks

!

Full report

Domain & DNS report for today.com ›

Mail

fail

20 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
  • !
    No key under common selectors
    DKIM · The _domainkey name exists but no DKIM key was found under the common selectors. Selectors are provider-specific; check yours with -selector.
    #7
  • !
    Not enabled
    DNSSEC · DNSSEC is not enabled for this domain. Consider enabling DNSSEC to protect against DNS spoofing attacks.
    #8
  • !
    Hosts without IPv6
    MX · The following MX hosts could not be resolved to IPv6 addresses: mxa-00176a04.gslb.pphosted.com, mxb-00176a04.gslb.pphosted.com, mx0a-00176a04.pphosted.com, mx0b-00176a04.pphosted.com
    #11
  • !
    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 today.com ›