SurfaceMap › r › riteaid.com

riteaid.com

Checked 2026-10-22 10:31 UTC · first added 2026-10-21

✗Problems found Score 69 of 100

Domain & DNS

warn

24 passed 2 warn 0 failed

Areas

iRegistration iDelegation !Nameservers ✓SOA !DNSSEC iRecords

Problems

!

Software version disclosed

Nameservers · These nameservers report their software version via version.bind/version.server, which helps attackers find known vulnerabilities: hope.ns.cloudflare.com: "2026.10.2"; quinton.ns.cloudflare.com: "2026.10.2". Hide or replace the version string.

#17
!

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 riteaid.com ›

Mail

fail

25 passed 5 warn 1 failed

Areas

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

Problems

✗

Weak DKIM key

DKIM · RSA keys shorter than 1024 bits can be cracked and are ignored by receivers (RFC 8301): mail (768 bits). Rotate to a 2048-bit key.

#23
!

Policy: quarantine

DMARC · DMARC policy is set to 'quarantine'. Consider upgrading to 'reject' for stronger protection once you've verified legitimate emails are passing authentication.

#4
!

Not enabled

DNSSEC · DNSSEC is not enabled for this domain. Consider enabling DNSSEC to protect against DNS spoofing attacks.

#8
!

Single MX host, no backup

MX · Only one MX record found. For better email reliability, consider adding at least one backup MX server.

#12
!

Key in test mode

DKIM · These keys have t=y, so receivers treat DKIM failures as a test: mail. Remove t=y once DKIM works.

#24
!

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 riteaid.com ›