iPGaze

DNS records for linode.com

linode.com resolves to 2 IPv4 addresses and 2 IPv6 addresses, it is served by 6 nameservers (a4-64.akam.net), and accepts mail via 2 MX records.

Run a live lookup ↗

A records (IPv4)

TTL 20s95.100.104.24
TTL 20s95.100.104.4

AAAA records (IPv6)

TTL 20s2a02:26f0:fd00:38::b81a:378c
TTL 20s2a02:26f0:fd00:38::b81a:3789

MX records (mail servers)

Priority 10mxb-00190b01.gslb.pphosted.com
Priority 10mxa-00190b01.gslb.pphosted.com

NS records (nameservers)

NS 1a4-64.akam.net
NS 2a3-67.akam.net
NS 3a16-64.akam.net
NS 4a12-65.akam.net
NS 5a7-65.akam.net
NS 6a1-249.akam.net

TXT records

TXT 1MS=ms97506004
TXT 2google-site-verification=MKjylAJoYaAgAUs3p_fqq-Ni_It6Aj2AyS1sIEi0Ei4
TXT 3b9vnqzyfsl9dkjxtlp39xz1pn6qnmnsc
TXT 4v=spf1 a:outbound.mail.linode.com include:sendersv4b.mail.linode.com include:_spf.google.com include:mktomail.com include:spf-009e7401.pphosted.com ip4:52.71.30.102 ip4:97.107.141.36 ip6:2600:3c03::f03c:91ff:fe6e:fda0 ip4:66.175.208.40 ip6:2600:3c03:e000:af2::1 ip4:173.255.198.11 ip4:66.175.211.242 ip6:2600:3c00:e000:07e9::1 ip6:2600:3c03:e000:bfc::1 ip4:67.231.149.131 ip4:67.231.157.127 ip6:2620:100:9001:583::1 ip6:2620:100:9005:57f::1 -all
TXT 5smartsheet-site-validation=8ft-lsEKUr2E2GS-WYZeQWn934ECdlgu
TXT 6google-site-verification=H-BI4P6tXdj3SCxfVfiJQbxX3p94r8_SXuGTkndOybI
TXT 7dtm-domain-verification=YkO_GJYRE_W_o9DSThOI34Yy6aHLITePNr-3zaVl_H4
TXT 8google-site-verification=pUYBl3BO8G5rgQrfHoQDxfu7HqKEcnGY7v20KYL0vNQ
TXT 91password-site-verification=XG272XO7HRFGBCO7BHRE55R6ME
TXT 10MS=ms93951359

SOA (Start of Authority)

Primary NSa1-249.akam.net
Hostmasterdns.linode.com
Serial2026061414
Refresh4200s
Retry3600s
Expire2419200s
Min TTL86400s

More lookups for linode.com

DNS records map a domain like linode.com 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.