racingpost.com

Checked 22 October 2026, 10:24 UTC · via 8.8.8.8
✗Problems found
23 passed 3 warnings 1 failed 3 info

SPF

pass

SPF record published

Found

Record
v=spf1 ip4:80.71.28.96/27 ip4:213.146.171.170 ip4:5.148.11.184/29 ip4:89.197.166.102/32 ip4:141.0.153.62/32 ip4:35.197.203.186/32 ip4:35.242.182.162/32 ip4:54.77.160.217 ip4:195.2.224.0/24 ip4:54.77.160.217 ip4:91.186.188.141/26 ip4:83.217.246.94/26 ip4:83.231.158.129/26 ip4:91.186.188.8/26 ip4:185.160.252.224 ip4:217.20.46.224/27 ip4:20.76.43.33 ip4:20.73.222.54 ip4:199.255.192.0/22 ip4:199.127.232.0/22 ip4:54.240.0.0/18 ip4:69.169.224.0/20 ip4:23.249.208.0/20 ip4:23.251.224.0/19 ip4:76.223.176.0/20 ip4:54.240.64.0/19 include:_spf.google.com include:eu._netblocks.mimecast.com include:us._netblocks.mimecast.com include:spf.protection.outlook.com include:shops.shopify.com include:mail.zendesk.com -all
DNS lookups
6 of 10
Void lookups
0 of 2

Checks

  • ✓ No deprecated ptr mechanism #1
    No ptr mechanism found in SPF record.
  • ✓ 6 of 10 DNS lookups #2
    SPF record needs 6 DNS lookups (limit is 10).
  • ✓ Ends with -all #3
    SPF record properly uses -all to restrict unauthorized senders.
  • ✓ Record published #6
    SPF record exists for this domain.
  • ✓ Single record #16
    Exactly one SPF record is published.
  • ✓ Valid syntax #25
    All SPF mechanisms and modifiers are valid.
  • ✓ 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.racingpost.com)

Found

Record
v=DMARC1; p=reject; rua=mailto:fd8ea8f3879f579@rep.dmarcanalyzer.com,mailto:dmarc@spotlightsportsgroup.com; ruf=mailto:fd8ea8f3879f579@for.dmarcanalyzer.com,mailto:dmarc@spotlightsportsgroup.com; fo=1;
Found at
_dmarc.racingpost.com
External report address
mailto:fd8ea8f3879f579@rep.dmarcanalyzer.com (authorized)
External report address
mailto:dmarc@spotlightsportsgroup.com (authorized)
External report address
mailto:fd8ea8f3879f579@for.dmarcanalyzer.com (authorized)
TagValueMeaning
vDMARC1Version
prejectPolicy
ruamailto:fd8ea8f3879f579@rep.dmarcanalyzer.com,mailto:dmarc@spotlightsportsgroup.comAggregate report addresses
rufmailto:fd8ea8f3879f579@for.dmarcanalyzer.com,mailto:dmarc@spotlightsportsgroup.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:fd8ea8f3879f579@rep.dmarcanalyzer.com, mailto:dmarc@spotlightsportsgroup.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

fail

No keys found under the checked selectors

Found

Selectors
None found
_domainkey
NXDOMAIN

Checks

  • ✗
    No DKIM keys published
    _domainkey.racingpost.com does not exist (NXDOMAIN), so no DKIM keys are published. DKIM helps prevent email spoofing. Configure DKIM with your email service provider.
    #7

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 91.220.42.201 A 195.130.217.201 A 195.130.217.241 A 91.220.42.211 A 91.220.42.241 A 195.130.217.211eu-smtp-inbound-1.mimecast.com ✓ eu-smtp-inbound-2.mimecast.com ✓ eu-smtp-inbound-2.mimecast.com ✓ eu-smtp-inbound-2.mimecast.com ✓ eu-smtp-inbound-2.mimecast.com ✓ eu-smtp-inbound-1.mimecast.com ✓
10eu-smtp-inbound-2.mimecast.comA 195.130.217.241 A 195.130.217.201 A 91.220.42.211 A 91.220.42.241 A 91.220.42.201 A 195.130.217.211eu-smtp-inbound-2.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 ✓ eu-smtp-inbound-2.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