Dashboard / Social Media / telegram.org
Social Media /

Telegram

telegram.org

Last checked: 3 weeks ago

Download Report
Partially Compliant
MGv6C-1.0
73%
Partial Support
Works on IPv6 Only?
Website Ready
DNS Ready
Email Not Ready

IPv6 Addresses Detected

2001:67c:4e8:f004::9

IPv4 Addresses Detected

149.154.167.99

Network Information

WHOIS

IPv6 Network

Organization
MNT-TELEGRAM
Country
VG
ASN
AS62041 Telegram - Telegram Messenger Inc, VG
Network
2001:67c:4e8::/48

IPv4 Network

Organization
MNT-TELEGRAM
Country
AG
ASN
AS62041 Telegram - Telegram Messenger Inc, VG
Network
149.154.164.0/22

Web Services

35%
7/8
AAAA Record

The domain has at least one IPv6 address (AAAA DNS record).

✓ 2001:67c:4e8:f004::9

+1
Globally Routable IPv6

The IPv6 addresses are publicly routable — not link-local, ULA, loopback or documentation ranges.

✓ All addresses are globally routable.

+1
HTTP over IPv6

Website reachable on port 80 when connecting via IPv6.

✓ HTTP (port 80) responds over IPv6 — 855ms TTFB.

+1
HTTPS over IPv6

Website reachable on port 443 when connecting via IPv6.

✓ HTTPS (port 443) responds over IPv6 — 513ms TTFB.

+1
IPv6-Only Reachability

Website responds when connected exclusively over IPv6, with no IPv4 fallback. Simulates what happens when IPv4 is turned off.

✓ Site is fully reachable via IPv6-only.

+1
TLS Certificate Valid (IPv6)

The SSL/TLS certificate is valid, not expired, and matches the domain when connected via IPv6.

✓ Certificate valid — issued by C = US, ST = Arizona, L = Scottsdale, O = "GoDaddy.com, Inc.", OU = http://certs.godaddy.com/repository/, CN = Go Daddy Secure Certificate Authority - G2, expires Sep 12 13:36:48 2026 GMT

+1
Dual-Stack (IPv4 + IPv6)

The domain has both A and AAAA records for backwards compatibility during the IPv6 transition.

✓ Domain has both A and AAAA records.

+1
HTTP/3 (QUIC)

Server advertises HTTP/3 support via the Alt-Svc: h3 header.

✗ No HTTP/3 support detected.

0

DNS & DNSSEC

25%
3/5
NS Has AAAA Record

At least one authoritative nameserver has an IPv6 address (AAAA record).

✓ Nameserver has IPv6 address.

+1
NS Reachable via IPv6

Authoritative nameserver accepts TCP connections on port 53 over IPv6.

✓ Nameserver is reachable via IPv6 on port 53.

+1
NS Answers Queries via IPv6

Nameserver actually resolves DNS queries when asked over IPv6 — not just TCP open, but functionally answering.

✓ DNS queries answered over IPv6.

+1
DNSSEC Validated

Full DNSSEC chain-of-trust validation passes. Prevents DNS cache poisoning and spoofing.

✗ DNSSEC validation failed or zone is unsigned.

0
Reverse DNS (PTR)

A PTR record exists in ip6.arpa for the IPv6 address. Important for email delivery and network diagnostics.

✗ No PTR record found.

0
DS Record at Parent

Delegation Signer record exists in the parent zone.

✗ No DS record at parent.

RRSIG Valid

RRSIG signatures are present and not expired.

✗ No valid RRSIG found.

Signing Algorithm

The cryptographic algorithm used for DNSSEC signing.

No DNSKEY record found.

Email Services

25%
3/6
MX Record Exists

The domain has at least one MX (Mail Exchange) DNS record pointing to a mail server.

✓ MX record found.

+1
MX Server Has IPv6

The highest-priority MX server resolves to an IPv6 address (AAAA record).

✗ MX server has no IPv6 address.

0
SMTP Reachable via IPv6

The MX server accepts SMTP connections (port 25) over IPv6 and responds with a 220 banner.

✗ SMTP is not reachable over IPv6.

0
STARTTLS over IPv6

The MX server supports STARTTLS encryption when connected over IPv6.

✗ STARTTLS not available over IPv6.

0
SPF Record

A TXT record with v=spf1 exists, declaring which servers may send email for this domain.

✓ SPF record found.

+1
DKIM Selector

A DKIM public key is published at a common selector, enabling email signature verification.

DKIM selector found: mail._domainkey

DMARC Record

A DMARC policy record exists at _dmarc.<domain>, enabling email authentication reporting.

✓ DMARC record found.

+1

IPv4 Baseline

15%
3/3
A Record

The domain has at least one IPv4 address (A DNS record).

✓ 149.154.167.99

+1
HTTP over IPv4

Website reachable on port 80 when connecting via IPv4.

✓ HTTP (port 80) responds over IPv4 — 859ms TTFB.

+1
HTTPS over IPv4

Website reachable on port 443 when connecting via IPv4.

✓ HTTPS (port 443) responds over IPv4 — 505ms TTFB.

+1

Render-Path Dependencies

not weighted

An AAAA record on this domain says nothing about the stylesheets, scripts and fonts the page then loads from somewhere else. Those are scored here, separately, because a blended figure would flatter both numbers. This score does not affect the 73% above.

Not measured

The dependency chain could not be walked because this check predates dependency scoring. This is recorded as unmeasured rather than counted against the domain.

DNS Resolution Performance

Comparison of A (IPv4) vs AAAA (IPv6) query times across resolvers and transports. Shows median (p50) of 3 samples.

Resolver Transport A (IPv4) AAAA (IPv6) Delta
System Default 20.56 ms (p95: 22.47) 23.72 ms (p95: 30.12) +3.2 ms
Google IPv4 23.22 ms (p95: 84.25) 36.48 ms (p95: 96.74) +13.3 ms
Google IPv6 23.15 ms (p95: 33.05) 26.94 ms (p95: 90.66) +3.8 ms
Cloudflare IPv4 25.54 ms (p95: 33.3) 23.61 ms (p95: 33.2) -1.9 ms
Cloudflare IPv6 28.68 ms (p95: 28.7) 28.5 ms (p95: 29.53) -0.2 ms
Tamper-evident evidence record

This result is backed by an HMAC-SHA256 signed evidence record. Scan the code or follow the link to verify the audit trail independently.

5a2c03c5-f9ba-4336-81e9-6429d9ab92bb
View Audit Trail →

Score History

Check History

Last 9 checks

Date Score Status Triggered By
08 Aug 2026
18:20 UTC 		73 % Partial manual
08 Aug 2026
10:46 UTC 		73 % Partial manual
01 Aug 2026
03:22 UTC 		73 % Partial scheduled
01 Aug 2026
02:38 UTC 		73 % Partial scheduled
04 Jul 2026
03:25 UTC 		69 % Partial scheduled
13 Jun 2026
01:05 UTC 		69 % Partial scheduled
07 Mar 2026
01:16 UTC 		73 % Partial manual
06 Mar 2026
19:09 UTC 		73 % Partial manual
06 Mar 2026
18:48 UTC 		73 % Partial manual