ripleys.com

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

SPF

fail

SPF record published

Found

Record
v=spf1 mx a include:_netblocks.mimecast.com include:spf.protection.outlook.com include:_spf.brainier.com include:us._netblocks.mimecast.com include:shops.shopify.com include:sent-via.netsuite.com include:spf.yourpayroll.io include:mailsenders.netsuite.com include:servers.mcsv.net include:satisfilabs.com ip4:24.227.92.32/27 ip4:192.169.177.219 ip4:50.57.197.234 ip4:209.118.211.154 ip4:208.86.171.32 ip4:72.35.67.91 ip4:208.86.170.134 ip4:208.86.170.218 ip4:64.78.151.128/26 ip4:216.241.183.0/24 ip4:167.89.26.204 ip4:65.60.11.140 ip4:96.46.249.240 ip4:167.89.88.69 ip4:167.89.2.97 ip4:167.89.24.241 ip4:167.89.26.204 ip4:167.89.47.137 ip4:205.201.128.0/20 ip4:198.2.128.18 ip4:148.105.0.0/16 include:spf-us.emailsignatures365.com -all
DNS lookups
21 of 10
Void lookups
0 of 2

Checks

  • ✓ No deprecated ptr mechanism #1
    No ptr mechanism found in SPF record.
  • ✗
    21 DNS lookups, over the limit of 10
    SPF record needs 21 DNS lookups (including nested includes), more than the limit of 10. Receivers will return a permerror; reduce includes or flatten the record.
    #2
  • ✓ 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.ripleys.com)

Found

Record
v=DMARC1 ;p=none
Found at
_dmarc.ripleys.com
TagValueMeaning
vDMARC1Version
pnonePolicy

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.
  • !
    No aggregate reports (rua)
    DMARC record has no rua tag, so you receive no aggregate reports about who sends mail as your domain. Add rua=mailto:...
    #19

DKIM

warn

Selectors: selector1, selector2, s1, s2

Found

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

Checks

  • ✓ Keys found: selector1, selector2, s1, s2 #7
    DKIM keys found for this domain with selectors: selector1, selector2, s1, s2
  • !
    1024-bit DKIM key
    1024-bit RSA keys are the minimum and are considered weak today: selector1 (1024 bits), selector2 (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
10us-smtp-inbound-1.mimecast.comA 170.10.132.221 A 170.10.128.141 A 170.10.128.221 A 170.10.128.242 A 170.10.132.242 A 170.10.132.141us-smtp-inbound-2.mimecast.com ✓ us-smtp-inbound-2.mimecast.com ✓ us-smtp-inbound-2.mimecast.com ✓ us-smtp-inbound-2.mimecast.com ✓ us-smtp-inbound-1.mimecast.com ✓ us-smtp-inbound-1.mimecast.com ✓
10us-smtp-inbound-2.mimecast.comA 170.10.132.242 A 170.10.128.221 A 170.10.128.141 A 170.10.128.242 A 170.10.132.141 A 170.10.132.221us-smtp-inbound-1.mimecast.com ✓ us-smtp-inbound-1.mimecast.com ✓ us-smtp-inbound-1.mimecast.com ✓ us-smtp-inbound-1.mimecast.com ✓ us-smtp-inbound-1.mimecast.com ✓ us-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: us-smtp-inbound-1.mimecast.com, us-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
us-smtp-inbound-1.mimecast.comnone-
us-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