SurfaceMap › t › tottenhamhotspur.com

tottenhamhotspur.com

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

Domain & DNS

fail

24 passed 2 warn 1 failed

Areas

iRegistration iDelegation ✗Nameservers !SOA !DNSSEC iRecords

Problems

  • ✗
    No DNS over TCP
    Nameservers · DNS over TCP is required (RFC 7766); without it, large answers such as DNSSEC responses fail. Not answering over TCP: ns1.iptwins.net (188.165.162.43): read tcp 46.225.38.91:46740->188.165.162.43:53: i/o timeout.
    #19
  • !
    Unusual SOA timers
    SOA · negative caching TTL (minimum) 4d is outside 5m–1d (RFC 2308 recommends 1–3 hours). Current values: refresh 1d, retry 2h, expire 30d, negative TTL 4d.
    #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 tottenhamhotspur.com ›

Mail

fail

22 passed 5 warn 2 failed

Areas

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

Problems

  • ✗
    Multiple SPF records
    SPF · Found 2 SPF records. Publishing more than one v=spf1 record causes a permerror; merge them into a single record.
    #16
  • ✗
    Syntax errors
    SPF · Receivers reject the whole SPF record (permerror) because of: unknown mechanism ":smtp.ticketmaster.co.uk"; "include:": include needs a value; unknown mechanism "production.spf.ticketmaster.com".
    #25
  • !
    8 of 10 DNS lookups, with problems
    SPF · SPF record needs 8 DNS lookups (limit is 10). Problems found: include without a domain.
    #2
  • !
    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: eu-smtp-inbound-1.mimecast.com, eu-smtp-inbound-2.mimecast.com
    #11
  • !
    1024-bit DKIM key
    DKIM · 1024-bit RSA keys are the minimum and are considered weak today: mail (1024 bits), selector1 (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 tottenhamhotspur.com ›