jamieoliver.com

Checked 22 October 2026, 09:23 UTC · via 8.8.8.8
✗Problems found
19 passed 4 warnings 1 failed 4 info

SPF

pass

SPF record published

Found

Record
v=spf1 include:eu._netblocks.mimecast.com mx a ip4:94.136.40.63 ip4:193.33.147.118/32 ip4:193.33.147.254/32 ip4:54.229.75.177/32 ip4:52.18.143.12/32 ip4:35.190.247.0/24 ip4:64.233.160.0/19 ip4:66.102.0.0/20 ip4:66.249.80.0/20 ip4:72.14.192.0/18 ip4:74.125.0.0/16 ip4:108.177.8.0/21 ip4:173.194.0.0/16 ip4:209.85.128.0/17 ip4:216.58.192.0/19 ip4:216.239.32.0/19 ip6:2001:4860:4000::/36 ip6:2404:6800:4000::/36 ip6:2607:f8b0:4000::/36 ip6:2800:3f0:4000::/36 ip6:2a00:1450:4000::/36 ip6:2c0f:fb50:4000::/36 ip4:172.217.0.0/19 ip4:172.217.32.0/20 ip4:172.217.128.0/19 ip4:172.217.160.0/20 ip4:172.217.192.0/19 ip4:172.253.56.0/21 ip4:172.253.112.0/20 ip4:108.177.96.0/19 ip4:35.191.0.0/16 ip4:130.211.0.0/22 ip4:167.89.0.0/17 ip4:208.117.48.0/20 ip4:50.31.32.0/19 ip4:198.37.144.0/20 ip4:198.21.0.0/21 ip4:192.254.112.0/20 ip4:168.245.0.0/17 ip4:149.72.0.0/16 ip4:159.183.0.0/16 ip4:223.165.113.0/24 ip4:223.165.115.0/24 ip4:223.165.118.0/23 ip4:223.165.120.0/23 ip4:3.25.47.0/29 ip4:52.62.151.40 ip4:13.237.4.248 ip4:13.211.56.237 ip4:3.26.58.204/30 ip4:54.252.22.127 ip4:54.206.207.130 ip4:3.26.82.216/29 ip4:3.26.88.88/29 ip4:3.26.88.244/30 ip4:3.106.23.177/29 ip4:3.107.43.16/28 include:servers.mcsv.net include:shops.shopify.com include:mail.zendesk.com include:fdspfus.freshemail.io include:fdspfeuc.freshemail.io include:fdspfind.freshemail.io include:spf.skillcast.com ~all
DNS lookups
10 of 10
Void lookups
0 of 2

Checks

  • ✓ No deprecated ptr mechanism #1
    No ptr mechanism found in SPF record.
  • ✓ 10 of 10 DNS lookups #2
    SPF record needs 10 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

fail

p=none (_dmarc.jamieoliver.com)

Found

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

Checks

  • ✗
    Policy: none (monitoring only)
    DMARC policy is set to 'none', which only monitors but doesn't protect against spoofing. Consider upgrading to 'quarantine' or ideally 'reject'.
    #4
  • ✓ Record published #5
    DMARC record exists for this domain.
  • ✓ Valid syntax #17
    DMARC record syntax is valid.
  • ✓ Aggregate reports enabled #19
    Aggregate reports are sent to: mailto:55afa06141@rep.dmarcanalyzer.com
  • ✓ External report addresses authorized #29
    Report addresses in other domains have published their authorization.

DKIM

warn

No keys found under the checked selectors

Found

Selectors
None found
_domainkey
NOERROR

Checks

  • !
    No key under common selectors
    The _domainkey name exists but no DKIM key was found under the common selectors. Selectors are provider-specific; check yours with -selector.
    #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.211 A 195.130.217.201 A 91.220.42.241 A 195.130.217.211 A 91.220.42.201 A 195.130.217.241eu-smtp-inbound-2.mimecast.com ✓ eu-smtp-inbound-1.mimecast.com ✓ eu-smtp-inbound-1.mimecast.com ✓ eu-smtp-inbound-1.mimecast.com ✓ lookup failed eu-smtp-inbound-2.mimecast.com ✓
10eu-smtp-inbound-2.mimecast.comA 195.130.217.211 A 195.130.217.241 A 91.220.42.211 A 195.130.217.201 A 91.220.42.241 A 91.220.42.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-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.
  • i
    Could not be checked
    The reverse lookup failed for: 91.220.42.201.
    #30

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