Email Authentication Check

bmg.name

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

All data shown is public and sourced from DNS.

Last checked about 21 hours ago

0 out of 110
Very Good

bmg.name enforces a strict DMARC reject policy, instructing receivers to block unauthenticated emails. SPF is correctly configured with a strict policy (-all), specifying which servers may send on its behalf. Overall, bmg.name has solid email authentication with room for minor improvements.

Curious how this compares? See the DMARC posture of the top 100 domains.

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.bmg.name TXT Entry:

v=DMARC1; p=reject; rua=mailto:[email protected],mailto:[email protected]; ruf=mailto:[email protected]

Policy (p)

reject

DKIM Alignment (adkim)

Relaxed (default)

SPF Alignment (aspf)

Relaxed (default)

Reporting (RUA/RUF)

Aggregate 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
  • Track all sending sources and authentication results
  • Email alerts when your DNS records change
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.bmg.name 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.

bmg.name TXT SPF Entry:

v=spf1 ip4:108.178.43.106 include:spf.greengeeks.net include:spf.efwd.registrar-servers.com -all

Syntax Check

OK

DNS Lookup Count

3 / 10 max

Root-level mechanisms requiring DNS queries: 2.

Void Lookups

0 / 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)

bmg.name (Root SPF Record)
108.178.43.106

This record also contains:

include:spf.greengeeks.net include:spf.efwd.registrar-servers.com
include:relay.mailchannels.net
23.83.208.0/20
35.85.190.185/32
include:spf.efwd.registrar-servers.com
209.105.246.192/28
198.54.122.192/26
162.255.118.0/26
198.54.122.0/28
162.255.118.240/29
63.250.43.96/27
198.177.126.16/28

DNS Lookup Details

1
include:
spf.greengeeks.net
Valid

SPF record found

Lookup cost: 1
Included by bmg.name

TXT Record

v=spf1 include:relay.mailchannels.net -all

Processed recursively per RFC 7208

2
include:
relay.mailchannels.net
Valid

SPF record found

Lookup cost: 0
Included by spf.greengeeks.net

TXT Record

v=spf1 ip4:23.83.208.0/20 ip4:35.85.190.185/32 ~all

Processed recursively per RFC 7208

3
include:
spf.efwd.registrar-servers.com
Valid

SPF record found

Lookup cost: 0
Included by bmg.name

TXT Record

v=spf1 ip4:209.105.246.192/28 ip4:198.54.122.192/26 ip4:162.255.118.0/26 ip4:198.54.122.0/28 ip4:162.255.118.240/29 ip4:63.250.43.96/27 ip4:198.177.126.16/28 ?all

Processed recursively per RFC 7208

0

TLS Security

10 / 10 points

Score Breakdown

TLS-RPT record configured
+5
MTA-STS policy configured
+5

TLS-RPT (Reporting)

TLS-RPT Reporting Configured

Current TLS-RPT Entry:

v=TLSRPTv1; rua=mailto:[email protected]

Reporting URIs:

MTA-STS (Policy)

MTA-STS Policy Configured

Current MTA-STS Entry:

v=STSv1; id=20260410

Policy ID:

20260410

Know when your DNS records change

The check you just ran shows your current configuration. But DNS records change, sometimes without you knowing. A well-meaning IT change, a third-party provider update, or an unauthorized modification can break your email delivery overnight.

Configuration Drift

IT changes that accidentally break authentication

Provider Updates

Third-party services changing their SPF includes

Unauthorized Changes

Attackers modifying records to send as you

DMARCTrust monitors your DNS records continuously. When something changes, you get an email alert with exactly what changed and why it matters. No more surprises when customers complain their emails bounced.

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 and certificate status when present.

Why it matters

Healthy authentication improves delivery and blocks spoofing. Major inbox providers increasingly expect DMARC and aligned SPF/DKIM from 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

Monitor your email authentication 24/7

This check shows a snapshot. With DMARCTrust, you get continuous monitoring of your DMARC reports and DNS records, with instant alerts when something changes.