Email Authentication Check

telegram.org

This gap analysis verifies compliance with email authentication standards to protect against spoofing and phishing.

All data displayed is public and provided by the DNS system.

Last checked about 3 hours ago

0 out of 110
Good
0

DMARC Check Results

45 / 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) not configured (optional)
0 / 5

DMARC check passed: properly configured

DMARC record is valid and configured correctly.

_dmarc.telegram.org TXT Entry:

v=DMARC1; p=reject; aspf=r; sp=reject; rua=mailto:[email protected]

Policy (p)

reject

DKIM Alignment (adkim)

Relaxed (default)

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)

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)

5 / 20 points

Score Breakdown

BIMI record published
+5
BIMI record valid
0 / 5
Logo URL accessible and valid SVG
0 / 5
No VMC certificate configured (optional)
0 / 5

BIMI record must start with 'v=BIMI1'.

Current BIMI Entry:

v=spf1 ip4:95.161.64.0/28 ip4:149.154.167.0/26 ip4:149.154.160.0/20 ip4:95.161.64.17/32 ip4:149.154.162.247/32 mx include:aspmx.googlemail.com -all

Logo URL

Missing logo URL (l=)

Mark Certificate

No certificate URL provided (a=). Optional when using self-asserted logos.

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.

telegram.org TXT SPF Entry:

v=spf1 ip4:95.161.64.0/28 ip4:95.161.64.16/32 ip4:149.154.160.0/20 ip4:95.161.64.17/32 ip4:149.154.162.125/32 ip4:149.154.162.247/32 -all

Syntax Check

OK

DNS Lookup Count

0 / 10 max

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)

telegram.org (Root SPF Record)
95.161.64.0/28
95.161.64.16/32
149.154.160.0/20
95.161.64.17/32
149.154.162.125/32
149.154.162.247/32
0

TLS Security

0 / 10 points

Score Breakdown

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

TLS-RPT (Reporting)

TLS-RPT Not Configured

Publish a TXT record at _smtp._tls.telegram.org with v=TLSRPTv1 and reporting URI (rua=).

MTA-STS (Policy)

MTA-STS Not Configured

Publish a TXT record at _mta-sts.telegram.org with v=STSv1 and policy ID (id=).

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.

Email Security Configuration

How telegram.org configures email authentication

DMARC Domain Policy
Configured
v=DMARC1; p=reject; aspf=r; sp=reject; rua=mailto:[email protected]
p=reject DKIM: relaxed SPF: relaxed Reports enabled
SPF Sender Authorization
Configured
v=spf1 ip4:95.161.64.0/28 ip4:95.161.64.16/32 ip4:149.154.160.0/20 ip4:95.161.64.17/32 ip4:149.154.162.125/32 ip4:149.154.162.247/32 -all
-all 6 IPs
BIMI Brand Indicator
Configured
v=spf1 ip4:95.161.64.0/28 ip4:149.154.167.0/26 ip4:149.154.160.0/20 ip4:95.161.64.17/32 ip4:149.154.162.247/32 mx include:aspmx.googlemail.com -all

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

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.