tottenhamhotspur.com

Checked 22 October 2026, 11:11 UTC · via 8.8.8.8
✗Problems found
22 passed 5 warnings 2 failed 3 info

SPF

fail

SPF record published

Found

Record
v=spf1 include:_spf.mlsend.com include:eu._netblocks.mimecast.com ip4:217.10.147.146 ip4:217.10.147.138 ip4:209.104.49.110 ip4:209.104.49.136 ip4:77.75.136.240 ip4:109.74.243.202 ip4:109.74.243.203 a :smtp.ticketmaster.co.uk include:spf.protection.outlook.com include:europe.spf.ticketmaster.com include: production.spf.ticketmaster.com include:mail.zendesk.com include:_spf.psm.knowbe4.com ip4:80.6.91.150 ip4:217.68.20.25 ip4:62.216.247.190 -all
DNS lookups
8 of 10
Void lookups
0 of 2
Records published
2
Problem
include without a domain

Checks

  • ✓ No deprecated ptr mechanism #1
    No ptr mechanism found in SPF record.
  • !
    8 of 10 DNS lookups, with problems
    SPF record needs 8 DNS lookups (limit is 10). Problems found: include without a domain.
    #2
  • ✓ Ends with -all #3
    SPF record properly uses -all to restrict unauthorized senders.
  • ✓ Record published #6
    SPF record exists for this domain.
  • ✗
    Multiple SPF records
    Found 2 SPF records. Publishing more than one v=spf1 record causes a permerror; merge them into a single record.
    #16
  • ✗
    Syntax errors
    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
  • ✓ No void lookups #26
    All include/redirect targets exist.
  • ✓ No overly broad IP ranges #27
    All ip4/ip6 ranges are narrow enough.

DMARC

pass

p=reject (_dmarc.tottenhamhotspur.com)

Found

Record
v=DMARC1; p=reject; rua=mailto:e666c23d9685141@rep.dmarcanalyzer.com; ruf=mailto:e666c23d9685141@for.dmarcanalyzer.com; fo=1;
Found at
_dmarc.tottenhamhotspur.com
External report address
mailto:e666c23d9685141@rep.dmarcanalyzer.com (authorized)
External report address
mailto:e666c23d9685141@for.dmarcanalyzer.com (authorized)
TagValueMeaning
vDMARC1Version
prejectPolicy
ruamailto:e666c23d9685141@rep.dmarcanalyzer.comAggregate report addresses
rufmailto:e666c23d9685141@for.dmarcanalyzer.comFailure report addresses
fo1Failure reporting options

Checks

  • ✓ Policy: reject #4
    DMARC policy is set to 'reject', which provides the strongest protection against email spoofing.
  • ✓ Record published #5
    DMARC record exists for this domain.
  • ✓ Valid syntax #17
    DMARC record syntax is valid.
  • ✓ Applies to 100% of mail #18
    DMARC policy applies to all failing mail.
  • ✓ Aggregate reports enabled #19
    Aggregate reports are sent to: mailto:e666c23d9685141@rep.dmarcanalyzer.com
  • ✓ Subdomain policy: reject #20
    Subdomains are covered by policy 'reject'.
  • ✓ External report addresses authorized #29
    Report addresses in other domains have published their authorization.

DKIM

warn

Selectors: mail, selector1, selector2, s1, s2

Found

Selectors
mail, selector1, selector2, s1, s2
_domainkey
NOERROR
SelectorKeyFlags
mailRSA 1024 bits
selector1RSA 1024 bits
selector2RSA 2048 bits
s1RSA 2048 bits
s2RSA 2048 bits

Checks

  • ✓ Keys found: mail, selector1, selector2, s1, s2 #7
    DKIM keys found for this domain with selectors: mail, selector1, selector2, s1, s2
  • !
    1024-bit DKIM key
    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
  • ✓ No problematic flags #24
    No keys in test mode, revoked, or limited to SHA-1.

DNSSEC

warn

Not signed

Found

DNSKEY records
No (0)
DS at parent
No

Checks

  • !
    Not enabled
    DNSSEC is not enabled for this domain. Consider enabling DNSSEC to protect against DNS spoofing attacks.
    #8

MX

warn

2 mail servers

Found

PriorityHostRecordsReverse DNS
10eu-smtp-inbound-1.mimecast.comA 195.130.217.241 A 91.220.42.211 A 91.220.42.241 A 195.130.217.211 A 91.220.42.201 A 195.130.217.201eu-smtp-inbound-1.mimecast.com ✓ eu-smtp-inbound-1.mimecast.com ✓ eu-smtp-inbound-1.mimecast.com ✓ eu-smtp-inbound-1.mimecast.com ✓ eu-smtp-inbound-2.mimecast.com ✓ eu-smtp-inbound-1.mimecast.com ✓
20eu-smtp-inbound-2.mimecast.comA 91.220.42.201 A 91.220.42.211 A 195.130.217.241 A 91.220.42.241 A 195.130.217.211 A 195.130.217.201eu-smtp-inbound-2.mimecast.com ✓ eu-smtp-inbound-1.mimecast.com ✓ eu-smtp-inbound-1.mimecast.com ✓ eu-smtp-inbound-2.mimecast.com ✓ eu-smtp-inbound-2.mimecast.com ✓ eu-smtp-inbound-1.mimecast.com ✓

Checks

  • ✓ 2 MX records #9
    Found 2 MX records for this domain.
  • ✓ All hosts resolve #10
    All MX records resolve to valid IP addresses.
  • !
    Hosts without IPv6
    The following MX hosts could not be resolved to IPv6 addresses: eu-smtp-inbound-1.mimecast.com, eu-smtp-inbound-2.mimecast.com
    #11
  • ✓ Redundant MX hosts #12
    Found 2 MX records, which provides redundancy for email delivery.
  • ✓ At most 5 MX records #13
    Found 2 MX records, which is within the recommended range (1-5).
  • ✓ No localhost targets #14
    No MX records pointing to localhost found.
  • ✓ No private IP addresses #15
    No MX records resolving to private IP addresses found.
  • ✓ No CNAME targets #22
    No MX records point to a CNAME.
  • ✓ Reverse DNS confirmed #30
    All 12 MX addresss have a PTR record that resolves back to them.

TLS

warn

no MTA-STS · no TLS-RPT · DANE on 0 of 2 MX hosts

Found

DANE (TLSA records)

MX hostTLSADNSSEC
eu-smtp-inbound-1.mimecast.comnone-
eu-smtp-inbound-2.mimecast.comnone-

Checks

  • !
    Not configured
    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
  • i
    Not configured
    TLS-RPT lets senders report TLS delivery problems to you. It is most useful together with MTA-STS or DANE.
    #35
  • i
    Not used
    No MX host publishes TLSA records. DANE lets senders verify your mail server's certificate through DNSSEC; it requires DNSSEC on the MX host's zone.
    #36

BIMI

info

No BIMI record

Checks

  • i
    Not configured
    BIMI shows your logo next to your mail in supporting mail clients. It requires DMARC enforcement.
    #38