iPGaze

DNS records for telegram.org

telegram.org resolves to 1 IPv4 address and 1 IPv6 address, it is served by 4 nameservers (ns-cloud-b3.googledomains.com), and accepts mail via 2 MX records.

Run a live lookup ↗

A records (IPv4)

TTL 243s149.154.167.99

AAAA records (IPv6)

TTL 108s2001:67c:4e8:f004::9

MX records (mail servers)

Priority 10mx101.telegram.org
Priority 15mx110.telegram.org

NS records (nameservers)

NS 1ns-cloud-b3.googledomains.com
NS 2ns-cloud-b2.googledomains.com
NS 3ns-cloud-b1.googledomains.com
NS 4ns-cloud-b4.googledomains.com

TXT records

TXT 1v=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
TXT 2yahoo-verification-key=NRNCv6/IcZMkSv28KI97E4zgZVMkk4PejCwNSh8So2k=
TXT 3google-site-verification=R-3XYX47JUVHva3pnhnyjx5D72PtSnjtLMLj_tymTAc
TXT 4google-site-verification=hAtj8VzR8lGDcv80yGd0ST-pMHU8WNU0lkswaau3v2w

SOA (Start of Authority)

Primary NSns-cloud-b1.googledomains.com
Hostmasterdns.jomax.net.telegram.org
Serial2017053111
Refresh28800s
Retry7200s
Expire604800s
Min TTL600s

More lookups for telegram.org

DNS records map a domain like telegram.org to the servers and services behind it. A and AAAA records point to IPv4 and IPv6 addresses, MX records route email, NS records delegate authority to nameservers, TXT records hold verification and policy data (such as SPF), and the SOA record describes the zone. Values are cached by resolvers for the length of each record's TTL, so a recent change may not appear everywhere at once. To check any other domain, use the DNS Lookup tool.