Yes — telegram.company has IPv6.

Has both IPv4 (A) and IPv6 (AAAA) addresses.

IPv6 readiness

Works over IPv6, with one gap: its nameservers lack IPv6.

Website over IPv6 telegram.company has 4 IPv6 addresses and answers on every one we tested (4 more not tested). ✓ 2600:1f18:6a07:601:6471:b5e4:ef15:3b72 answers · 443✓ 2600:1f1c:6db:8801:46fe:f5ec:31a8:82f8 answers · 443✓ 2406:da1e:214:c901:49:871:e9e1:eb92 answers · 443✓ 2a05:d014:179b:c400:2fc6:8141:276a:b7e9 answers · 443– 2a01:4ff:1f0:dd50::1 not tested– 2a05:d018:1d22:801:a216:a799:8c87:df21 not tested– 2a01:4f8:1c1e:d6f1::1 not tested– 2a05:d018:1d22:800:6673:f7c3:558e:5d73 not tested	yes
www over IPv6 www.telegram.company has 4 IPv6 addresses and answers on every one we tested (4 more not tested). ✓ 2a01:4ff:1f0:dd50::1 answers · 443✓ 2a01:4f8:1c1e:d6f1::1 answers · 443✓ 2a05:d018:1d22:801:a216:a799:8c87:df21 answers · 443✓ 2a05:d014:179b:c400:2fc6:8141:276a:b7e9 answers · 443– 2a05:d018:1d22:800:6673:f7c3:558e:5d73 not tested– 2600:1f18:6a07:601:6471:b5e4:ef15:3b72 not tested– 2600:1f1c:6db:8801:46fe:f5ec:31a8:82f8 not tested– 2406:da1e:214:c901:49:871:e9e1:eb92 not tested	yes
Mail servers (MX) have IPv6 No MX records, so mail goes to the domain's own address (implicit MX). It has an AAAA record.	yes
Nameservers have IPv6 No nameserver has an AAAA record — an IPv6-only resolver can't reach this domain's DNS. ns1.dns-redirect.com ✗ns2.dns-redirect.com ✗	no

HTTPS over IPv6 · not part of the grade yet
Loads over IPv6 with a valid certificate after 1 redirect: HTTP 403.

https://telegram.company/ via 2600:1f18:6a07:601:6471:b5e4:ef15:3b72 → 301https://expireddomains.com/domain/telegram.company?utm_source=redi via 2606:4700:20::681a:e7a → 403

works

What's keeping telegram.company from an A

Nameservers without IPv6
ns1.dns-redirect.com, ns2.dns-redirect.com all have no AAAA record, so a resolver that only speaks IPv6 can't look your domain up. Most DNS providers offer IPv6 nameservers; ask yours, or move DNS to one that does.

Check again

telegram.company Has IPv6

A (IPv4)	5.78.156.59 76.223.91.20 46.62.237.138 195.201.128.179 5.161.47.86
AAAA (IPv6)	2600:1f18:6a07:601:6471:b5e4:ef15:3b72 2600:1f1c:6db:8801:46fe:f5ec:31a8:82f8 2406:da1e:214:c901:49:871:e9e1:eb92 2a05:d014:179b:c400:2fc6:8141:276a:b7e9 2a01:4ff:1f0:dd50::1 2a05:d018:1d22:801:a216:a799:8c87:df21 2a01:4f8:1c1e:d6f1::1 2a05:d018:1d22:800:6673:f7c3:558e:5d73

www.telegram.company Has IPv6

A (IPv4)	5.78.156.59 76.223.91.20 46.62.237.138 195.201.128.179 5.161.47.86
AAAA (IPv6)	2a01:4ff:1f0:dd50::1 2a01:4f8:1c1e:d6f1::1 2a05:d018:1d22:801:a216:a799:8c87:df21 2a05:d014:179b:c400:2fc6:8141:276a:b7e9 2a05:d018:1d22:800:6673:f7c3:558e:5d73 2600:1f18:6a07:601:6471:b5e4:ef15:3b72 2600:1f1c:6db:8801:46fe:f5ec:31a8:82f8 2406:da1e:214:c901:49:871:e9e1:eb92

Browsers on dual-stack networks will usually pick IPv6 here (the "Happy Eyeballs" algorithm races both and prefers v6).

Copy the evidence — a citation-ready record of this measurement

IPv6 measurement: telegram.company
Measured 2026-11-03 20:01:40 UTC by aaaa.bot (one server on Fly.io, region iad)

A (IPv4):    5.78.156.59, 76.223.91.20, 46.62.237.138, 195.201.128.179, 5.161.47.86
AAAA (IPv6): 2600:1f18:6a07:601:6471:b5e4:ef15:3b72, 2600:1f1c:6db:8801:46fe:f5ec:31a8:82f8, 2406:da1e:214:c901:49:871:e9e1:eb92, 2a05:d014:179b:c400:2fc6:8141:276a:b7e9, 2a01:4ff:1f0:dd50::1, 2a05:d018:1d22:801:a216:a799:8c87:df21, 2a01:4f8:1c1e:d6f1::1, 2a05:d018:1d22:800:6673:f7c3:558e:5d73
www AAAA:    2a01:4ff:1f0:dd50::1, 2a01:4f8:1c1e:d6f1::1, 2a05:d018:1d22:801:a216:a799:8c87:df21, 2a05:d014:179b:c400:2fc6:8141:276a:b7e9, 2a05:d018:1d22:800:6673:f7c3:558e:5d73, 2600:1f18:6a07:601:6471:b5e4:ef15:3b72, 2600:1f1c:6db:8801:46fe:f5ec:31a8:82f8, 2406:da1e:214:c901:49:871:e9e1:eb92

Readiness grade B: Works over IPv6, with one gap: its nameservers lack IPv6.
- Website over IPv6: telegram.company has 4 IPv6 addresses and answers on every one we tested (4 more not tested).
    2600:1f18:6a07:601:6471:b5e4:ef15:3b72: answers (TCP 443)
    2600:1f1c:6db:8801:46fe:f5ec:31a8:82f8: answers (TCP 443)
    2406:da1e:214:c901:49:871:e9e1:eb92: answers (TCP 443)
    2a05:d014:179b:c400:2fc6:8141:276a:b7e9: answers (TCP 443)
    2a01:4ff:1f0:dd50::1: not tested
    2a05:d018:1d22:801:a216:a799:8c87:df21: not tested
    2a01:4f8:1c1e:d6f1::1: not tested
    2a05:d018:1d22:800:6673:f7c3:558e:5d73: not tested
- www over IPv6: www.telegram.company has 4 IPv6 addresses and answers on every one we tested (4 more not tested).
    2a01:4ff:1f0:dd50::1: answers (TCP 443)
    2a01:4f8:1c1e:d6f1::1: answers (TCP 443)
    2a05:d018:1d22:801:a216:a799:8c87:df21: answers (TCP 443)
    2a05:d014:179b:c400:2fc6:8141:276a:b7e9: answers (TCP 443)
    2a05:d018:1d22:800:6673:f7c3:558e:5d73: not tested
    2600:1f18:6a07:601:6471:b5e4:ef15:3b72: not tested
    2600:1f1c:6db:8801:46fe:f5ec:31a8:82f8: not tested
    2406:da1e:214:c901:49:871:e9e1:eb92: not tested
- Mail servers (MX) have IPv6: No MX records, so mail goes to the domain's own address (implicit MX). It has an AAAA record.
- Nameservers have IPv6: No nameserver has an AAAA record — an IPv6-only resolver can't reach this domain's DNS.

Reachability = a TCP connection opened on port 443 (or 80).

HTTPS over IPv6 (not graded): Loads over IPv6 with a valid certificate after 1 redirect: HTTP 403.
    https://telegram.company/ via 2600:1f18:6a07:601:6471:b5e4:ef15:3b72 -> HTTP 301, certificate: valid
    https://expireddomains.com/domain/telegram.company?utm_source=redi via 2606:4700:20::681a:e7a -> HTTP 403, certificate: valid
DNS answers via DNS-over-HTTPS (Cloudflare). Method: https://aaaa.bot/method
Permanent link: https://aaaa.bot/r/QUnlbj8Xyv

Permanent link: aaaa.bot/r/QUnlbj8Xyv · How we measure

Checked 2026-11-03 20:01:40 UTC. Full DNS report: dns.pizza/domain/telegram.company · Age, certificate and blocklists: how.is/telegram.company · JSON: /api/v1/telegram.company