Authentication Records Check for

indeed.com

Instant checks for DMARC, SPF, and BIMI with clear, actionable guidance.

All data displayed is public and provided by the DNS system. Use of this website is subject to our Terms of Service.

Last checked about 9 hours ago

0 out of 100
Very Good

Domain Health Score

Your domain has strong email authentication. A few improvements can get you to a perfect score.

SPF
Sender Policy Framework
30 / 30
DMARC
Domain-based Message Authentication
50 / 50
BIMI
Brand Indicators for Message Identification
0 / 20
0

DMARC Check Results

50 / 50 points

Score Breakdown

DMARC record published
+10
Syntax valid
+5
Reject policy (maximum protection)
+20
Aggregate reporting (rua) configured and verified
+10
Forensic reporting (ruf) configured
+5

DMARC Check Passed: Properly Configured

DMARC record is valid and configured correctly.

_dmarc.indeed.com TXT Entry:

v=DMARC1; p=reject; sp=reject; rua=mailto:[email protected],mailto:[email protected]; ruf=mailto:[email protected]; adkim=r; aspf=r; pct=100

Policy (p)

reject

DKIM Alignment (adkim)

Relaxed (r)

SPF Alignment (aspf)

Relaxed (r)

Understanding Alignment Modes

DKIM Alignment (adkim)

Relaxed mode: The DKIM signature's domain can be a subdomain of the "From" header domain.

SPF Alignment (aspf)

Relaxed mode: The SPF "Return-Path" domain can be a subdomain of the "From" header domain.

Note: When alignment parameters are not specified, DMARC defaults to relaxed mode for both DKIM and SPF alignment.

Reporting (RUA/RUF)

Aggregate Reports

Configured
External Domain Verification

Verification successful

Forensic Reports

Configured
External Domain Verification

Verification successful

Add Our Monitoring System

You can add our monitoring system alongside your existing setup. DMARC supports multiple mailto: addresses, giving you additional visibility and backup reporting.

  • Automated DMARC report processing every 5 minutes
  • Clear insights and actionable recommendations
  • Track all sending sources and authentication results
0

BIMI Check (default selector)

0 / 20 points

Score Breakdown

BIMI record published (optional)
0 / 5

No BIMI Record Found

Publish a TXT record at default._bimi.indeed.com with v=BIMI1, logo URL (l=) and optional verified mark certificate (a=).

0

SPF Record Check Results

30 / 30 points

Score Breakdown

SPF record published
+10
Syntax valid
+5
Hard fail policy (-all)
+10
No configuration warnings
+5

SPF record is valid.

indeed.com TXT SPF Entry:

v=spf1 include:mail.zendesk.com include:mktomail.com include:spf.mptx.jp include:_netblocks2.google.com include:spf.haihaimail.jp include:_spf1.indeed.com -all

Syntax Check

OK

DNS Lookup Count

10 / 10 max

Close to RFC limit!

Root-level mechanisms requiring DNS queries: 6.

Void Lookups

2 / 2 max

Default Policy

-all

Fail: Reject emails from unauthorized servers (recommended for production)

All Authorized IP Addresses

Grouped by DNS record source (includes and sub-includes)

include:mail.zendesk.com
103.151.192.0/23
185.12.80.0/22
188.172.128.0/20
192.161.144.0/20
216.198.0.0/18
include:mktomail.com
199.15.212.0/22
72.3.185.0/24
72.32.154.0/24
72.32.217.0/24
72.32.243.0/24
94.236.119.0/26
37.188.97.188/32
185.28.196.0/22
192.28.128.0/18
103.237.104.0/22
130.248.172.0/24
130.248.173.0/24
include:spf.mptx.jp
121.50.56.0/24
18.180.53.0/24
106.186.67.0/24
106.186.92.192/26
125.29.57.64/26
106.185.82.0/23
106.185.84.0/23
106.185.96.0/23
106.185.98.0/23
106.185.100.0/23
35.72.225.0/25
57.181.227.128/26
210.169.34.0/26
include:_netblocks2.google.com | Google
2001:4860:4000::/36
2404:6800:4000::/36
2607:f8b0:4000::/36
2800:3f0:4000::/36
2a00:1450:4000::/36
2c0f:fb50:4000::/36
include:spf.haihaimail.jp
58.191.37.0/24
58.191.38.0/24
58.191.39.0/24
218.251.75.0/24
58.191.56.0/24
121.87.8.0/24
121.87.10.0/24
121.87.12.0/24
121.87.20.0/24
121.87.22.0/24
121.87.24.0/24
121.87.26.0/24
121.87.51.0/24
128.27.33.0/24
128.27.34.0/24
128.27.35.0/24
128.27.36.0/24
128.27.37.0/24
include:_spf1.indeed.com
4.7.16.128/26
35.190.247.0/24
35.191.0.0/16
38.108.186.0/24
64.233.160.0/19
66.102.0.0/20
66.249.80.0/20
72.14.192.0/18
74.125.0.0/16
108.177.8.0/21
108.177.96.0/19
130.211.0.0/22
172.217.0.0/19
172.217.32.0/20
172.217.128.0/19
172.217.160.0/20

This record also contains:

include:_spf2.indeed.com
include:_spf2.indeed.com
172.253.56.0/21
172.217.192.0/19
172.253.112.0/20
173.194.0.0/16
198.58.75.0/25
205.201.128.0/20
207.191.44.144/28
209.85.128.0/17
209.137.158.128/25
209.137.135.192/26

This record also contains:

include:_spf3.indeed.com
include:_spf3.indeed.com
216.58.192.0/19
216.239.32.0/19
208.74.204.0/22
46.19.168.0/23
5.61.117.96/28
5.61.117.112/28
198.2.128.0/18
74.217.56.176/28

DNS Lookup Details

1
include:
mail.zendesk.com
Valid

SPF record found

Lookup cost: 0
Included by indeed.com

TXT Record

v=spf1 ip4:103.151.192.0/23 ip4:185.12.80.0/22 ip4:188.172.128.0/20 ip4:192.161.144.0/20 ip4:216.198.0.0/18 ~all

Processed recursively per RFC 7208

2
include:
mktomail.com
Valid

SPF record found

Lookup cost: 0
Included by indeed.com

TXT Record

v=spf1 ip4:199.15.212.0/22 ip4:72.3.185.0/24 ip4:72.32.154.0/24 ip4:72.32.217.0/24 ip4:72.32.243.0/24 ip4:94.236.119.0/26 ip4:37.188.97.188/32 ip4:185.28.196.0/22 ip4:192.28.128.0/18 ip4:103.237.104.0/22 ip4:130.248.172.0/24 ip4:130.248.173.0/24 ~all

Processed recursively per RFC 7208

3
include:
spf.mptx.jp
Valid

SPF record found

Lookup cost: 0
Included by indeed.com

TXT Record

v=spf1 ip4:121.50.56.0/24 ip4:18.180.53.0/24 ip4:106.186.67.0/24 ip4:106.186.92.192/26 ip4:125.29.57.64/26 ip4:106.185.82.0/23 ip4:106.185.84.0/23 ip4:106.185.96.0/23 ip4:106.185.98.0/23 ip4:106.185.100.0/23 ip4:35.72.225.0/25 ip4:57.181.227.128/26 ip4:210.169.34.0/26 ~all

Processed recursively per RFC 7208

4
include:
_netblocks2.google.com | Google
Valid

SPF record found

Lookup cost: 0
Included by indeed.com

TXT Record

v=spf1 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 ~all

Processed recursively per RFC 7208

5
include:
spf.haihaimail.jp
Valid

SPF record found

Lookup cost: 0
Included by indeed.com

TXT Record

v=spf1 ip4:58.191.37.0/24 ip4:58.191.38.0/24 ip4:58.191.39.0/24 ip4:218.251.75.0/24 ip4:58.191.56.0/24 ip4:121.87.8.0/24 ip4:121.87.10.0/24 ip4:121.87.12.0/24 ip4:121.87.20.0/24 ip4:121.87.22.0/24 ip4:121.87.24.0/24 ip4:121.87.26.0/24 ip4:121.87.51.0/24 ip4:128.27.33.0/24 ip4:128.27.34.0/24 ip4:128.27.35.0/24 ip4:128.27.36.0/24 ip4:128.27.37.0/24 ~all

Processed recursively per RFC 7208

6
include:
_spf1.indeed.com
Valid

SPF record found

Lookup cost: 1
Included by indeed.com

TXT Record

v=spf1 ip4:4.7.16.128/26 ip4:35.190.247.0/24 ip4:35.191.0.0/16 ip4:38.108.186.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:108.177.96.0/19 ip4:130.211.0.0/22 ip4:172.217.0.0/19 ip4:172.217.32.0/20 ip4:172.217.128.0/19 ip4:172.217.160.0/20 include:_spf2.indeed.com -all

Processed recursively per RFC 7208

7
include:
_spf2.indeed.com
Valid

SPF record found

Lookup cost: 1
Included by _spf1.indeed.com

TXT Record

v=spf1 ip4:172.253.56.0/21 ip4:172.217.192.0/19 ip4:172.253.112.0/20 ip4:173.194.0.0/16 ip4:198.58.75.0/25 ip4:205.201.128.0/20 ip4:207.191.44.144/28 ip4:209.85.128.0/17 ip4:209.137.158.128/25 ip4:209.137.135.192/26 include:_spf3.indeed.com -all

Processed recursively per RFC 7208

8
include:
_spf3.indeed.com
Valid

SPF record found

Lookup cost: 2
Included by _spf2.indeed.com

TXT Record

v=spf1 ip4:216.58.192.0/19 ip4:216.239.32.0/19 ip4:208.74.204.0/22 ip4:46.19.168.0/23 ip4:5.61.117.96/28 ip4:5.61.117.112/28 ip4:198.2.128.0/18 ip4:74.217.56.176/28 exists:%{ir}.mta._spf.indeed.com exists:%{i}._spf.mta.salesforce.com -all

Processed recursively per RFC 7208

9
exists:
%{ir}.mta._spf.indeed.com
Not exists

Domain does not exist

Lookup cost: 1
10
exists:
%{i}._spf.mta.salesforce.com
Not exists

Domain does not exist

Lookup cost: 1

Email Security Configuration

How indeed.com configures email authentication

DMARC Domain Policy
Configured
v=DMARC1; p=reject; sp=reject; rua=mailto:[email protected],mailto:[email protected]; ruf=mailto:[email protected]; adkim=r; aspf=r; pct=100
p=reject DKIM: relaxed SPF: relaxed Reports enabled
SPF Sender Authorization
Configured
v=spf1 include:mail.zendesk.com include:mktomail.com include:spf.mptx.jp include:_netblocks2.google.com include:spf.haihaimail.jp include:_spf1.indeed.com -all
-all 6 includes
BIMI Brand Indicator
Not set
No BIMI record configured for this domain

Change History

Monitoring started January 10, 2026

Configuration changes will appear here when detected

Check Another Domain

Run a free email authentication check (DMARC, SPF, BIMI).

We will generate a shareable URL for your domain.

Try popular examples: google.com, amazon.com, booking.com

Explore Other Domains

Discover how other organizations configure their email authentication

Popular Domains

Frequently checked

Well-Configured

Reject policy + valid SPF

Same Policy

Also using reject

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

About This Checker

What we check

We analyze your domain's email authentication: DMARC policy and alignment, SPF record and includes, and BIMI logo/CV when present.

Why it matters

Healthy authentication improves delivery and blocks spoofing. Major inbox providers increasingly require DMARC and robust SPF/DKIM practices for senders.

Included features

  • DMARC syntax, policy, and reporting validation
  • SPF record evaluation and include analysis
  • DKIM/SPF alignment interpretation
  • BIMI record and VMC detection
  • Clear setup and remediation guidance

Related Tools

The Best Way to Monitor Your DMARC Performance

Don't rely on snapshots. Get the most accurate, real-time insights into your email delivery and reputation with DMARCTrust.