Dashboard / Social Media / telegram.org
Social Media /

Telegram

telegram.org

Last checked: 1 month 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, VG
Network
2001:67c:4e8::/48

IPv4 Network

Organization
MNT-TELEGRAM
Country
AG
ASN
AS62041 TELEGRAM, 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 — 851ms TTFB.

+1
HTTPS over IPv6

Website reachable on port 443 when connecting via IPv6.

✓ HTTPS (port 443) responds over IPv6 — 509ms 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 — 860ms TTFB.

+1
HTTPS over IPv4

Website reachable on port 443 when connecting via IPv4.

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

+1

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 12.89 ms (p95: 23.83) 6 ms (p95: 6.04) -6.9 ms
Google IPv4 17.34 ms (p95: 18.18) 16.91 ms (p95: 24.18) -0.4 ms
Google IPv6 18.7 ms (p95: 33.65) 28.21 ms (p95: 28.31) +9.5 ms
Cloudflare IPv4 9.81 ms (p95: 20.43) 9.6 ms (p95: 20.03) -0.2 ms
Cloudflare IPv6 19.69 ms (p95: 20.35) 16.72 ms (p95: 19.24) -3 ms
Verification ID: 6b7e1d1a-6f2c-4bfc-b4cf-60fa475d8687 View Audit Trail

Score History

Check History

Last 3 checks

Date Score Status Triggered By
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