Email authentication check

telegram.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 about 8 hours ago
Needs attention

telegram.org has email authentication in place, with important improvements still available.

telegram.org has strong outbound authentication. Adding inbound transport security would complete the picture.

80 out of 110
1 of 4 checks passed
DMARC 45 / 50 · Optional SPF 30 / 30 · Passed BIMI 5 / 20 · Failed TLS 0 / 10 · Optional
Last checked about 8 hours ago
Compare with other domains
DMARC SPF BIMI TLS

DMARC

Optional

Domain-based Message Authentication

45 / 50

Strict reject policy enforced

DMARC record is valid and configured correctly.

_dmarc.telegram.org TXT
v=DMARC1; p=reject; aspf=r; sp=reject; rua=mailto:[email protected]

Score breakdown

  • DMARC record published +10
  • Syntax valid +5
  • Reject policy (maximum protection) +20
  • Aggregate reporting (rua) configured and verified +10
  • Failure reporting (ruf) not configured (optional) 0 / 5

Configuration

Policy (p)
reject
DKIM alignment (adkim)
Relaxed (default)
SPF alignment (aspf)
Relaxed (r)
Subdomain policy (sp)
reject

Reporting (RUA / RUF)

Aggregate reports Passed
mailto:[email protected]
External domain verification successful
Failure reports Optional
Not configured
Optional failure reporting is not configured
RFC 9989 note on p=reject
RFC 9989 cautions against p=reject for domains whose users post to mailing lists, and §7.4 requires receivers to treat p=reject as p=quarantine unless their own analysis justifies rejecting. For transactional or marketing-only domains, p=reject stays appropriate; mailbox domains should consider p=quarantine with sp=reject on non-sending subdomains.

SPF

Passed

Sender Policy Framework

30 / 30

Hard-fail policy, within lookup limits

SPF record is valid and complies with RFC 7208.

telegram.org TXT
v=spf1 ip4:95.161.64.0/28 ip4:95.161.64.16/30 ip4:149.154.160.0/20 ip4:149.154.162.125/32 ip4:149.154.162.247/32 -all

Score breakdown

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

Configuration

Default policy
-all (hard fail)
DNS lookups
0 / 10 max
Void lookups
0 / 2 max
Syntax check
OK

Authorized IP addresses

telegram.org

95.161.64.0/28 95.161.64.16/30 149.154.160.0/20 149.154.162.125/32 149.154.162.247/32

BIMI

Failed

Brand Indicators for Message Identification

5 / 20

BIMI record has configuration errors

BIMI record must start with 'v=BIMI1'.

default._bimi.telegram.org TXT
v=spf1 ip4:95.161.64.0/28 ip4:149.154.167.0/26 ip4:149.154.160.0/20 ip4:95.161.64.16/30 ip4:149.154.162.247/32 mx include:aspmx.googlemail.com -all

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

Configuration

Logo (l)
Not configured
Mark certificate (a)
Not configured
Selector
default
Note
SVG content is not parsed, for safety

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

Start monitoring

telegram.org 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. A few improvements would strengthen telegram.org's email authentication posture.

Keep telegram.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 telegram.org View plans First checked 5 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 reject

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.