Email authentication check

trccnh.org

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 2 days ago
Needs attention

trccnh.org 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.

68 out of 110
0 of 4 checks passed
Last checked 2 days ago
Compare with other domains

DMARC

Optional

Domain-based Message Authentication

42 / 50

Quarantine policy enabled

DMARC record is valid and configured correctly.

_dmarc.trccnh.org TXT
v=DMARC1; p=quarantine; rua=mailto:[email protected]; ruf=mailto:[email protected]; fo=1

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
Failure reporting (fo)
1

Reporting (RUA / RUF)

Aggregate reports Passed
External domain verification successful
Failure reports Passed
External domain verification successful

SPF

Optional

Sender Policy Framework

21 / 30

SPF record is valid with warnings

SPF record is valid but has warnings: Explicit '+' qualifier is redundant (it's the default) and can be removed from: ip4:162.241.216.38

trccnh.org TXT
v=spf1 include:_spf.google.com +mx +a +ip4:162.241.216.38 ~all

Score breakdown

  • SPF record published +10
  • Syntax valid +5
  • Soft fail policy (~all) +6
  • Configuration warnings present 0 / 5

Configuration

Default policy
~all (soft fail)
DNS lookups
8 / 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 mx: trccnh.org Resolved

MX records found: 5

MX records

aspmx.l.google.com (priority: 1)

alt4.aspmx.l.google.com (priority: 10)

alt2.aspmx.l.google.com (priority: 5)

alt1.aspmx.l.google.com (priority: 5)

alt3.aspmx.l.google.com (priority: 10)

3 a: trccnh.org Resolved

A/AAAA records found: 1

Authorized IP addresses

trccnh.org

162.241.216.38

This record also contains

include:_spf.google.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
SPF configuration warning
Explicit '+' qualifier is redundant (it's the default) and can be removed from: ip4:162.241.216.38

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

5 / 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 +5
  • MTA-STS policy configured (optional) 0 / 5

Configuration

TLS-RPT
Configured
MTA-STS
Not configured
TLS-RPT reporting URIs
mailto:[email protected]

Transport checks

TLS-RPT (reporting) Configured
v=TLSRPTv1; rua=mailto:[email protected]

TLS-RPT record is valid and configured correctly.

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 trccnh.org.

Start monitoring

trccnh.org has a DMARC quarantine policy, directing unauthenticated emails to spam. An SPF record is published but has warnings that could affect delivery. A few improvements would strengthen trccnh.org's email authentication posture.

Keep trccnh.org 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 trccnh.org View plans First checked 2 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.