Email authentication check

stanford.edu

This check reviews the domain's email authentication setup to help protect against spoofing and phishing.

All data is public, sourced from DNS Last checked 1 day ago
Needs attention

stanford.edu has email authentication in place, with important improvements still available.

Some protections are present, but tightening the policy, reporting, or sender authorization would improve resilience.

64 out of 110
0 of 4 checks passed
DMARC 42 / 50 · Optional SPF 22 / 30 · Optional BIMI 0 / 20 · Optional TLS 0 / 10 · Optional
Last checked 1 day ago
Compare with other domains

DMARC

Optional

Domain-based Message Authentication

42 / 50

Quarantine policy enabled

DMARC record is valid and configured correctly.

_dmarc.stanford.edu TXT
v=DMARC1; p=quarantine; rua=mailto:[email protected]; ruf=mailto:[email protected];

Score breakdown

  • DMARC record published +10
  • Syntax valid +5
  • Quarantine policy +12
  • Aggregate reporting (rua) configured and verified +10
  • Failure reporting (ruf) configured +5

Configuration

Policy (p)
quarantine
DKIM alignment (adkim)
Relaxed (default)
SPF alignment (aspf)
Relaxed (default)
Subdomain policy (sp)
Inherits p=quarantine

Reporting (RUA / RUF)

Aggregate reports Passed
mailto:[email protected]
External domain verification successful
Failure reports Passed
mailto:[email protected]
External domain verification successful

SPF

Optional

Sender Policy Framework

22 / 30

SPF record is valid

SPF record is valid and complies with RFC 7208.

stanford.edu TXT
v=spf1 ip4:171.67.219.64/27 ip4:171.67.224.0/28 ip4:171.67.43.137 ip4:171.67.43.138 ip4:171.67.43.139 ip4:171.67.43.140 ip4:171.67.43.141 include:_spf.google.com include:_spf.qualtrics.com include:icpbounce.com include:spf.protection.outlook.com ip4:148.163.149.245 ip4:148.163.153.235 ip4:148.163.135.119 ip4:148.163.139.119 ip4:67.231.149.169 ip4:67.231.157.125 ip4:67.231.152.67 ip4:208.84.65.155 ?all

Score breakdown

  • SPF record published +10
  • Syntax valid +5
  • Neutral policy (?all) +2
  • No configuration warnings +5

Configuration

Default policy
?all (neutral)
DNS lookups
7 / 10 max
Void lookups
0 / 2 max
Syntax check
OK

DNS lookup detail

Each mechanism that may trigger a DNS query at delivery time.

1 include: _spf.google.com Valid

SPF record found

v=spf1 ip4:74.125.0.0/16 ip4:209.85.128.0/17 ip6:2001:4860:4864::/56 ip6:2404:6800:4864::/56 ip6:2607:f8b0:4864::/56 ip6:2800:3f0:4864::/56 ip6:2a00:1450:4864::/56 ip6:2c0f:fb50:4864::/56 ~all

Processed recursively per RFC 7208

2 include: _spf.qualtrics.com Valid

SPF record found

v=spf1 ip4:162.247.216.0/22 ip4:139.60.152.0/22 ip4:98.97.248.0/21 ip4:64.69.212.0/24 ip4:54.186.193.102/32 ip4:52.222.73.120/32 ip4:52.222.73.83 ip4:52.222.62.51 ip4:52.222.75.85 ip4:52.222.89.228 ip4:160.1.62.192 ip4:52.61.91.9 ip4:15.200.21.50 ip4:15.200.201.185 ip4:15.200.44.248 -all

Processed recursively per RFC 7208

3 include: icpbounce.com Valid

SPF record found

v=spf1 ip4:40.143.226.0/24 ip4:63.236.100.0/24 ip4:66.77.16.0/24 ip4:74.202.227.32/27 ip4:216.27.93.0/25 ip4:216.27.84.64/27 ip4:66.192.165.128/28 ip4:66.162.193.224/28 ip4:64.132.109.48/28 ip4:216.27.86.128/26 ip4:207.254.213.192/26 ip4:69.166.133.128/29 ip4:69.166.133.224/29 ip4:69.166.133.232/29 a mx -all

Processed recursively per RFC 7208

4 a: icpbounce.com Resolved

A/AAAA records found: 2

5 mx: icpbounce.com Resolved

MX records found: 1

MX records

bounces001.icpbounce.com (priority: 5)

6 include: spf.protection.outlook.com Valid

SPF record found

v=spf1 ip4:40.92.0.0/15 ip4:40.107.0.0/16 ip4:52.100.0.0/15 ip4:52.102.0.0/16 ip4:52.103.0.0/17 ip4:104.47.0.0/17 ip6:2a01:111:f400::/48 ip6:2a01:111:f403::/49 ip6:2a01:111:f403:8000::/51 ip6:2a01:111:f403:c000::/51 ip6:2a01:111:f403:f000::/52 -all

Processed recursively per RFC 7208

Authorized IP addresses

stanford.edu

171.67.219.64/27 171.67.224.0/28 171.67.43.137 171.67.43.138 171.67.43.139 171.67.43.140 171.67.43.141 148.163.149.245 148.163.153.235 148.163.135.119 148.163.139.119 67.231.149.169 67.231.157.125 67.231.152.67 208.84.65.155

This record also contains

include:_spf.google.com include:_spf.qualtrics.com include:icpbounce.com include:spf.protection.outlook.com

include:_spf.google.com

74.125.0.0/16 209.85.128.0/17 2001:4860:4864::/56 2404:6800:4864::/56 2607:f8b0:4864::/56 2800:3f0:4864::/56 2a00:1450:4864::/56 2c0f:fb50:4864::/56

include:_spf.qualtrics.com

162.247.216.0/22 139.60.152.0/22 98.97.248.0/21 64.69.212.0/24 54.186.193.102/32 52.222.73.120/32 52.222.73.83 52.222.62.51 52.222.75.85 52.222.89.228 160.1.62.192 52.61.91.9 15.200.21.50 15.200.201.185 15.200.44.248

include:icpbounce.com

40.143.226.0/24 63.236.100.0/24 66.77.16.0/24 74.202.227.32/27 216.27.93.0/25 216.27.84.64/27 66.192.165.128/28 66.162.193.224/28 64.132.109.48/28 216.27.86.128/26 207.254.213.192/26 69.166.133.128/29 69.166.133.224/29 69.166.133.232/29

include:spf.protection.outlook.com

40.92.0.0/15 40.107.0.0/16 52.100.0.0/15 52.102.0.0/16 52.103.0.0/17 104.47.0.0/17 2a01:111:f400::/48 2a01:111:f403::/49 2a01:111:f403:8000::/51 2a01:111:f403:c000::/51 2a01:111:f403:f000::/52

BIMI

Optional

Brand Indicators for Message Identification

0 / 20

No BIMI record published

No BIMI record found for selector 'default'.

Score breakdown

  • BIMI record published (optional) 0 / 5

Configuration

Logo (l)
Not configured
Mark certificate (a)
Not configured
Selector
default
Note
SVG content is not parsed, for safety
BIMI is optional
BIMI usually matters after DMARC enforcement is working. Use it for brand display, not as a replacement for SPF or DMARC.

TLS

Optional

Transport security · MTA-STS & TLS-RPT

0 / 10

Inbound transport protection not fully configured

MTA-STS and TLS-RPT are optional, but they protect inbound mail against transport downgrade attacks and give visibility into TLS delivery failures.

Score breakdown

  • TLS-RPT record configured (optional) 0 / 5
  • MTA-STS policy configured (optional) 0 / 5

Configuration

TLS-RPT
Not configured
MTA-STS
Not configured

Transport checks

TLS-RPT (reporting) Not configured

No TLS-RPT record found.

MTA-STS (policy) Not configured

No MTA-STS record found.

Protect inbound transport

Receiver Shield helps deploy, monitor, and safely enforce MTA-STS and TLS-RPT for stanford.edu.

Start monitoring

stanford.edu has a DMARC quarantine policy, directing unauthenticated emails to spam. SPF is configured, authorizing specific servers to send on its behalf. A few improvements would strengthen stanford.edu's email authentication posture.

Keep stanford.edu protected automatically

This check is a snapshot. DNS records drift when providers change, teams edit records, or unauthorized changes slip in. DMARCTrust watches the same authentication layer continuously and tells you when something moves.

DMARC report processing

Aggregate and failure DMARC reports are received, parsed, and turned into sender visibility without manual XML handling.

DNS change alerts

DNS checks run every 5 minutes for monitored domains, with email alerts when DMARC, SPF, BIMI, TLS-RPT, or MTA-STS records change.

Receiver Shield for inbound

Deploy, host, and safely enforce MTA-STS and TLS-RPT when this checker finds an inbound transport gap.

Start monitoring stanford.edu View plans First checked 7 months ago

Check another domain

Run a free email authentication check: DMARC, SPF, BIMI, TLS-RPT, and MTA-STS.

Try a popular example: google.com, amazon.com, booking.com
Explore

How other domains configure email authentication

Showing domains checked by our users. All data is from public DNS records.

Popular domains

Frequently checked

Well configured

Reject policy + valid SPF

Same policy

Also using quarantine

What we check

DMARC policy and alignment, SPF record and includes, BIMI logo and certificate, and inbound transport security with MTA-STS and TLS-RPT.

Why it matters

Healthy authentication improves delivery and blocks spoofing. Major inbox providers increasingly expect DMARC and aligned SPF or DKIM from senders.

What you get

Syntax, policy, reporting validation, include analysis, alignment interpretation, and clear setup guidance for every result.