returnpath.com

15-check dossier · scoreboard above, section details below

Get a pack →

Scanning…

dns

info

Open standalone →

resolving…

mx

info

Open standalone →

resolving mx…

spf

info

Open standalone →

resolving spf…

dmarc

info

Open standalone →

resolving dmarc…

dkim

info

Open standalone →

probing dkim selectors…

tls

info

Open standalone →

fetching tls cert…

redirects

info

Open standalone →

tracing redirects…

headers

info

Open standalone →

fetching headers…

cors

info

Open standalone →

sending preflight…

web-surface

info

Open standalone →

inspecting web surface…

dnssec

info

Open standalone →

checking dnssec…

mta-sts

info

Open standalone →

checking mta-sts…

tls-rpt

info

Open standalone →

checking tls-rpt…

whois

info

Open standalone →

resolving whois…

ct-log

info

Open standalone →

querying CT logs…

additional context — IP + user-agent lookups

lookups that complement a dossier — useful when investigating a finding, but not part of the dossier engine itself.

IP lookup — geolocation, ASN, ISP for any IP address surfaced by the DNS or redirect sections.
user-agent parser — the browser/OS/device the request came from.
single-record DNS lookup — drill into one record type at a time.

returnpath.com

15-check dossier · scoreboard above, section details below

Get a pack →

Mostly compliant · 5 items need attention

Aggregate grade across 15 checks. Auditors typically flag any High-severity finding.

Pass: 10
Warn: 5
Fail: 0

What an auditor would flag first

medium
Redirect chain
redirects to different domain: validity.com
SOC 2 CC6.6
low
DKIM
no DKIM selectors found — likely not configured
SOC 2 CC6.7
low
TLS certificate
cert expires in 69 days
SOC 2 CC6.6ISO 27001 A.13.1.1

Need this as an artifact your auditor can verify?

Your returnpath.com scan flagged 1 medium and 4 low findings. A signed pack covers the apex plus up to 100 CT-discovered subdomains, Ed25519-signed and ISO-timestamped, delivered in 10–30 minutes.

Get a pack →See methodology See a sample$29

Scanning…

15-check summary

DNS recordsA/AAAA records present
MX2 MX record(s) present
SPF-all hardfail — strict policy
DMARCp=reject — strict policy
DKIMno DKIM selectors found — likely not configured
TLS certificatecert expires in 69 days
Redirect chainredirects to different domain: validity.com
Security headers4 security header(s) missing
CORSno CORS headers — cross-origin requests blocked by default
Web surfaceHTTPS surface reachable (robots ✓, sitemap ✓, title ✓)
MTA-STSnot applicable: no _mta-sts TXT record
TLS-RPTnot applicable: no TLSRPT record
DNSSECDNSSEC not configured — no DS or DNSKEY records found
WHOISdomain registered until 2027-05-01
Certificate Transparencycheck failed: crt.sh: Error: crt.sh http 429; certspotter: Error: certspotter http 429

dns

info

Open standalone →

A/AAAA records present

Why it matters: Without authoritative A or AAAA records on the apex, the domain is unreachable. Missing baseline DNS shows up in vendor reviews as evidence of unmanaged infrastructure (SOC 2 CC6.6).

A: ttl=600 23.185.0.1
AAAA: ttl=600 2620:12a:8001::1
ttl=600 2620:12a:8000::1
NS: ttl=172800 ns-1418.awsdns-49.org.
ttl=172800 ns-1888.awsdns-44.co.uk.
ttl=172800 ns-68.awsdns-08.com.
ttl=172800 ns-987.awsdns-59.net.
SOA: ttl=900 ns-1888.awsdns-44.co.uk. awsdns-hostmaster.amazon.com. 1 7200 900 1209600 86400
CAA: —
TXT: ttl=600 "0ed1fe018a7ea06333817e4077ab6ba1b279ebb7a2"
ttl=600 "MS=9DABA85ADFE63ACDE113FC5976C6DCA8445B81F4"
ttl=600 "MS=ms31772095"
ttl=600 "adobe-idp-site-verification=578696d3832278b3ebee3d74eaf9a51115959db4a40e4229bb0787abba52753c"
ttl=600 "apple-domain-verification=UrHpETLTnzhBsaCx"
ttl=600 "atlassian-domain-verification=wOWhouBkJcuEM9yOshT2c6GPgFLMeUVwn90wSUx2SDOuNhHWN13ReutTOSNCvP1S"
ttl=600 "google-site-verification=6qBBpVKS8Ej5Gu56fUKOWzN05ctKPmH1lq1aRFUB48M"
ttl=600 "google-site-verification=LzzOFhRd2bY-drj-GtywHzATwFoMFZXfTXBs1XmrQvw"
ttl=600 "google-site-verification=PReoQr7L7xz-pjT66rev5gu8kerfOd5_jhPZ9V04rls"
ttl=600 "v=spf1 ip4:50.201.69.200 ip4:209.67.98.59 ip4:50.31.61.183 include:us._netblocks.mimecast.com include:sendgrid.net include:_spfblock.salesforce.com" " ip4:54.89.206.1 ip4:107.21.130.253 ip4:52.204.80.252 ip4:54.84.12.226 ip4:52.20.42.191 ip4:54.204.201.126 ip4:52.2.235.188 ip4:35.173.34.182 ip4:18.204.66.234 ip4:34.225.165.102 ip4:35.168.206.101 ip4:52.55.181.224" " include:_spf.google.com include:spf.mandrillapp.com include:mail.zendesk.com ip4:192.28.144.45 ip4:52.207.191.216/29 ip4:52.43.191.248/29 -all"
ttl=600 "validity-domain-monitoring=xhrvTxQCa26lHpkd0J2n0y6zq"

fetched 2026-05-23T08:26:55.104Z

dns

info

Open standalone →

resolving…

mx

info

Open standalone →

2 MX record(s) present

Why it matters: MX records direct inbound mail. Misconfiguration silently breaks email delivery and lets attackers stand up parallel MX hosts for spoofing campaigns (ISO 27001 A.8.21).

pri=10 us-smtp-inbound-1.mimecast.com.
pri=10 us-smtp-inbound-2.mimecast.com.

fetched 2026-05-23T08:26:55.018Z

mx

info

Open standalone →

resolving mx…

spf

info

Open standalone →

-all hardfail — strict policy

Why it matters: SPF tells receiving servers which hosts may send mail for the domain. Without it, any sender can forge the envelope-from — the primary mechanism behind business-email-compromise (SOC 2 CC6.7).

v=spf1 ip4:50.201.69.200 ip4:209.67.98.59 ip4:50.31.61.183 include:us._netblocks.mimecast.com include:sendgrid.net include:_spfblock.salesforce.com ip4:54.89.206.1 ip4:107.21.130.253 ip4:52.204.80.252 ip4:54.84.12.226 ip4:52.20.42.191 ip4:54.204.201.126 ip4:52.2.235.188 ip4:35.173.34.182 ip4:18.204.66.234 ip4:34.225.165.102 ip4:35.168.206.101 ip4:52.55.181.224 include:_spf.google.com include:spf.mandrillapp.com include:mail.zendesk.com ip4:192.28.144.45 ip4:52.207.191.216/29 ip4:52.43.191.248/29 -all

v=spf1
ip4:50.201.69.200
ip4:209.67.98.59
ip4:50.31.61.183
include:us._netblocks.mimecast.com
include:sendgrid.net
include:_spfblock.salesforce.com
ip4:54.89.206.1
ip4:107.21.130.253
ip4:52.204.80.252
ip4:54.84.12.226
ip4:52.20.42.191
ip4:54.204.201.126
ip4:52.2.235.188
ip4:35.173.34.182
ip4:18.204.66.234
ip4:34.225.165.102
ip4:35.168.206.101
ip4:52.55.181.224
include:_spf.google.com
include:spf.mandrillapp.com
include:mail.zendesk.com
ip4:192.28.144.45
ip4:52.207.191.216/29
ip4:52.43.191.248/29
-all

fetched 2026-05-23T08:26:55.163Z

spf

info

Open standalone →

resolving spf…

dmarc

info

Open standalone →

p=reject — strict policy

Why it matters: DMARC binds SPF and DKIM into an enforceable policy (quarantine or reject) and surfaces spoofing attempts via aggregate reports. `p=none` or absent means spoofing succeeds silently (SOC 2 CC6.7).

v=DMARC1; p=reject; rua=mailto:dmarc_agg@dmarc.250ok.net; ruf=mailto:dmarc_fr@dmarc.250ok.net; fo=1; pct=100; rf=afrf

v=: DMARC1
p=: reject
rua=: mailto:dmarc_agg@dmarc.250ok.net
ruf=: mailto:dmarc_fr@dmarc.250ok.net
fo=: 1
pct=: 100
rf=: afrf

fetched 2026-05-23T08:26:55.018Z

dmarc

info

Open standalone →

resolving dmarc…

dkim

low

Open standalone →

no DKIM selectors found — likely not configured

Why it matters: DKIM signs outbound mail so receivers can detect tampering. Missing selectors or rotated-away keys break DMARC alignment and let receivers downgrade trust (ISO 27001 A.8.24).

Recommendations

Enable DKIM signing in your mail provider and publish the provided TXT record
Common selectors: google._domainkey, selector1._domainkey (Microsoft), mail._domainkey

no DKIM record on probed selectors (default, google, k1, selector1, selector2, mxvault)

dkim

info

Open standalone →

probing dkim selectors…

tls

low

Open standalone →

cert expires in 69 days

Why it matters: A valid current TLS certificate is the baseline for data in transit. Expiry, weak chain, or hostname mismatch break HTTPS and fail PCI 4.2.1 / SOC 2 CC6.1.

Recommendations

Schedule certificate renewal — consider enabling auto-renewal

subject cn:: billing.returnpath.com
issuer:: R13 / Let's Encrypt
valid:: May 2 13:51:36 2026 GMT → Jul 31 13:51:35 2026 GMT
authorized:: yes
sha256:: 36:9D:B4:1C:DF:59:00:D3:46:28:37:C0:1B:99:08:32:AD:3E:87:F3:1E:ED:0C:1C:62:ED:7C:EE:C3:25:2D:1E
sans: billing.returnpath.com
blog.habeas.com
bondedsender.org
br.returnpath.com
brand.returnpath.com
careers.returnpath.com
careers.returnpath.net
clubinbox.com
connect.returnpath.com
corp.returnpath.net
de.returnpath.com
de.returnpath.net
emabrke.com
emailchallenge.returnpath.com
emailcopilot.com
emailheroes.com
emailheroes.org
emailintelligence.com
es.returnpath.com
es.returnpath.net
fr.returnpath.com
fr.returnpath.net
global.returnpath.net
habeas.com
it.returnpath.com
landing.returnpath.com
returnpath.biz
returnpath.ca
returnpath.com
returnpath.de
returnpath.fi
returnpath.fr
returnpath.it
returnpath.net
returnpath.nl
returnpath.org
returnpath.ru
senderindex.com
smartbounce.returnpath.com
stopemailfraud.returnpath.com
support.returnpath.com
support.returnpath.net
www.bondedsender.org
www.emabrke.com
www.emailcopilot.com
www.emailintelligence.com
www.habeas.com
www.returnpath.biz
www.returnpath.com
www.returnpath.de
www.returnpath.fi
www.returnpath.fr
www.returnpath.it
www.returnpath.net
www.returnpath.nl
www.returnpath.org
www.returnpath.ru

fetched 2026-05-23T08:26:54.962Z

tls

info

Open standalone →

fetching tls cert…

redirects

medium

Open standalone →

redirects to different domain: validity.com

Why it matters: Bare HTTP requests must redirect to HTTPS without dropping the user mid-chain. Plain-text fallback or open redirects fail PCI 4.2.1 and feed phishing chains (SOC 2 CC6.6).

Recommendations

Verify this cross-domain redirect is intentional (e.g. domain migration or CDN)
Ensure the destination domain is owned and expected — unintended redirects can leak traffic

final status: 200 · 3 hops

[301] https://returnpath.com/
[301] https://www.validity.com/products/returnpath/
[200] https://www.validity.com/everest/returnpath/

fetched 2026-05-23T08:26:55.436Z

redirects

info

Open standalone →

tracing redirects…

headers

low

Open standalone →

4 security header(s) missing

Why it matters: Security headers — HSTS, CSP, X-Frame-Options, Referrer-Policy — defend against XSS, clickjacking, and downgrade attacks. Absent headers map directly to OWASP ASVS V14 findings (ISO 27001 A.8.23).

Recommendations

Add response header — Content-Security-Policy: default-src 'self' (tune per app)
Add response header — X-Content-Type-Options: nosniff
Add response header — Referrer-Policy: strict-origin-when-cross-origin
Add permissions-policy response header

final url: https://www.validity.com/everest/returnpath/

security headers

strict-transport-security: max-age=63072000; includeSubDomains; preload
content-security-policy: —
x-frame-options: allow-from http://salesforce.com/
x-content-type-options: —
referrer-policy: —
permissions-policy: —

other headers

alt-svc: h3=":443"; ma=86400
cache-control: max-age=600, must-revalidate
cf-cache-status: DYNAMIC
cf-ray: a002adb06bf5e721-IAD
connection: keep-alive
content-encoding: br
content-type: text/html; charset=UTF-8
date: Sat, 23 May 2026 08:26:55 GMT
link: <https://www.validity.com/wp-json/>; rel="https://api.w.org/", <https://www.validity.com/wp-json/wp/v2/pages/32356>; rel="alternate"; title="JSON"; type="application/json"
server: cloudflare
set-cookie: __cf_bm=LRnKc.3zO28cS3C1GskhSakBGtfTFcaikKqWAk9JqKc-1779524815.4271154-1.0.1.1-RzALtaXCFfe2mbxEMNlSm_omqv8aEXZ.MOhyakdWBOJoHlRJVKyz1Hw_gNnads3Ulsmef9bCysg10DFQS3KM50iW0lYEfUjhJ4h4s2Ew.IWvjR2Ciw._jzV_nqYZe8B2; HttpOnly; SameSite=None; Secure; Path=/; Domain=www.validity.com; Expires=Sat, 23 May 2026 08:56:55 GMT
transfer-encoding: chunked
vary: Accept-Encoding, Accept-Encoding, Accept-Encoding, Accept-Encoding,Cookie
x-cache: HIT: 6
x-cache-group: normal
x-cacheable: SHORT
x-dlm-no-waypoints: true
x-powered-by: WP Engine

fetched 2026-05-23T08:26:55.477Z

headers

info

Open standalone →

fetching headers…

cors

info

Open standalone →

no CORS headers — cross-origin requests blocked by default

Why it matters: Overly permissive CORS (wildcard with credentials, or reflected origin) lets any origin read authenticated responses from this domain. OWASP A05 misconfiguration territory (NIST AC-4).

origin: https://drwho.me
method: GET
preflight status: 405

access-control-* headers

access-control-allow-origin: —
access-control-allow-methods: —
access-control-allow-headers: —
access-control-allow-credentials: —
access-control-max-age: —
access-control-expose-headers: —

no access-control-* headers returned — site does not advertise CORS to this origin

fetched 2026-05-23T08:26:55.070Z

cors

info

Open standalone →

sending preflight…

web-surface

info

Open standalone →

HTTPS surface reachable (robots ✓, sitemap ✓, title ✓)

Why it matters: Public files — robots.txt, sitemap.xml, head meta — are what attackers see first during reconnaissance. Misadvertised paths, stale sitemaps, and verbose generators leak more than intended (ISO 27001 A.8.9).

robots.txt

present

# Return Path robots file
User-agent: *

# Static Assets
Disallow: /rpstatic
Disallow: /rpasset
Disallow: /assets

# RP API
Disallow: /rpapi

# Internal Tools
Disallow: /internal-tools

# Custom RSS feeds
Disallow: /feed-blog-featured-resources/
Disallow: /feed-email-heroes/
Disallow: /feed-gem-featured-resources/
Disallow: /feed-sender-score-featured-resources/
Disallow: /feed-sender-score-content/

# Thanks
Disallow: /thanks
Disallow: /merci
Disallow: /vielen-dank
Disallow: /obrigado
Disallow: /gracias

# Gated resources
Disallow: /wp-content/uploads/*.pdf

# Open Trap Project
Disallow: /opencontacts

# Downloads that redirect (Obtained from Google Search Console)
Disallow: /de/downloads/kleine-zahlen-grose-wirkung
Disallow: /downloads/10-email-tips-to-keep-your-holidays-merry-bright
Disallow: /fr/telechargements/certification
Disallow: /es/descargas/certificacion-2
Disallow: /de/downloads/zertifizierung
Disallow: /fr/telechargements/inbox-insight-2
Disallow: /pt-br/downloads/certificacao
Disallow: /de/downloads/inbox-insight-5
Disallow: /es/descargas/inbox-insight-4
Disallow: /pt-br/downloads/inbox-insight
Disallow: /downloads/supercharge-your-subject-lines
Disallow: /fr/telechargements/multivariate-testing-fact-sheet
Disallow: /pt-br/downloads/multivariate-testing-fact-sheet
Disallow: /es/descargas/multivariate-testing-fact-sheet
Disallow: /de/downloads/multivariate-testing-fact-sheet
Disallow: /pt-br/downloads/professional-services-overview
Disallow: /de/downloads/real-time-email-validation
Disallow: /downloads/certification-standards-fact-sheet
Disallow: /downloads/email-subscriber-experience
Disallow: /downloads/email-blacklist-guide

# Sitemaps
Sitemap: https://returnpath.com/sitemap_index.xml
Sitemap: https://returnpath.com/page-sitemap.xml
Sitemap: https://returnpath.com/customer-success-sitemap.xml
Sitemap: https://returnpath.com/downloads-sitemap.xml
Sitemap: https://returnpath.com/email-university-sitemap.xml
Sitemap: https://returnpath.com/events-sitemap.xml
Sitemap: https://returnpath.com/games-sitemap.xml
Sitemap: https://returnpath.com/leadership-sitemap.xml
Sitemap: https://returnpath.com/newsroom-sitemap.xml
Sitemap: https://returnpath.com/videos-sitemap.xml
Sitemap: https://returnpath.com/webinars-sitemap.xml

web-surface

info

Open standalone →

inspecting web surface…

dnssec

low

Open standalone →

DNSSEC not configured — no DS or DNSKEY records found

Why it matters: DNSSEC cryptographically signs DNS responses, blocking cache-poisoning attacks. US federal civilian agencies are required to enable it under OMB M-22-09 (NIST SC-20).

Recommendations

Enable DNSSEC in your DNS provider's control panel and add the resulting DS record at your registrar

enabled: no
DS records: —
DNSKEY records: —

fetched 2026-05-23T08:26:55.024Z

dnssec

info

Open standalone →

checking dnssec…

mta-sts

info

Open standalone →

not applicable: no _mta-sts TXT record

Why it matters: MTA-STS forces inbound SMTP to use TLS and refuse downgraded connections. Without it, an in-path attacker can strip TLS and read mail in plaintext (SOC 2 CC6.7).

no _mta-sts TXT record

mta-sts

info

Open standalone →

checking mta-sts…

tls-rpt

info

Open standalone →

not applicable: no TLSRPT record

Why it matters: TLS-RPT publishes a reporting address for SMTP-TLS failures. Without it, downgrade attacks on inbound mail go unnoticed (SOC 2 CC7.2).

no TLSRPT record

tls-rpt

info

Open standalone →

checking tls-rpt…

whois

info

Open standalone →

domain registered until 2027-05-01

Why it matters: Registrar and expiry tell auditors the domain is owned, current, and not about to lapse. An expired or about-to-expire domain fails business-continuity evidence (SOC 2 A1.2).

registrar: Amazon Registrar, Inc.
created: 1999-02-16T05:00:00Z
expires: 2027-05-01T11:59:59Z
statuses: clientTransferProhibited https://icann.org/epp#clientTransferProhibited

fetched 2026-05-23T08:26:55.366Z

whois

info

Open standalone →

resolving whois…

ct-log

info

Open standalone →

check failed: crt.sh: Error: crt.sh http 429; certspotter: Error: certspotter http 429

Why it matters: Every certificate issued for this domain is published in Certificate Transparency logs — including subdomains you may have forgotten. Unknown subdomains in CT are pre-disclosed attack surface (ISO 27001 A.8.16).

crt.sh: Error: crt.sh http 429; certspotter: Error: certspotter http 429

ct-log

info

Open standalone →

querying CT logs…

additional context — IP + user-agent lookups

lookups that complement a dossier — useful when investigating a finding, but not part of the dossier engine itself.

IP lookup — geolocation, ASN, ISP for any IP address surfaced by the DNS or redirect sections.
user-agent parser — the browser/OS/device the request came from.
single-record DNS lookup — drill into one record type at a time.