iPGaze

DNS records for mozilla.org

mozilla.org resolves to 1 IPv4 address and 1 IPv6 address, it is served by 4 nameservers (ns7-66.akam.net), and accepts mail via 4 MX records.

Run a live lookup ↗

A records (IPv4)

TTL 319s35.190.14.201

AAAA records (IPv6)

TTL 38s2600:1901:0:c197::

MX records (mail servers)

Priority 10aspmx3.googlemail.com
Priority 5alt1.aspmx.l.google.com
Priority 5alt2.aspmx.l.google.com
Priority 1aspmx.l.google.com

NS records (nameservers)

NS 1ns7-66.akam.net
NS 2ns5-65.akam.net
NS 3ns4-64.akam.net
NS 4ns1-240.akam.net

TXT records

TXT 1_zojr3c56nq36tokzhnj9crit28tiqly
TXT 2google-site-verification=S3M17z96OKfZJ2dq7mYqQDfRWsEVjy3hdxaSyB72YPc
TXT 3zoom-domain-verification=ZOOM_verify_671ea7b9c47d4b7b8cc9441f40817e3e
TXT 4anthropic-domain-verification-w5rph5=bZ2V4N0ps4oFSU6yrv4DfD6nA
TXT 5google-site-verification=z68pON7CWSaZu_sBqDQofmDL19OVp3krGEjaDl7cSaU
TXT 6v=spf1 include:%{i}._ip.%{h}._ehlo.%{d}._spf.vali.email include:_spf.mozilla.com include:_spf.google.com include:spf.fundraiseup.com ~all
TXT 7google-site-verification=Brpe3hQpo9FlGIHMtK4ViKL60L0G8VM16nXopwVDoEU
TXT 8google-site-verification=Lo_B34AJAe70BQVNF1Fo1zGGJudPmw9bLTnP2C8lV-s
TXT 9ZOOM_verify_lGxIzL49Id7PipUgDgTd9K
TXT 10rz8t7zvjv5frpfbjs3y5n6g5tkw7gt2q
TXT 11bzbkzkxj2ws8gvtw6hpssfy7lv9kym88
TXT 12openai-domain-verification=dv-J6NgbJamHFrHSyNqlhElIX5K
TXT 13google-site-verification=Ep3NdzNxaf8Vl48dniNneaqm7JcWUiy3GjKS0wx5zQw
TXT 14google-site-verification=E1vBHtOW-D9IlAj-pbRM-8PrOSiPDT48lrwRlW82ysw
TXT 15google-site-verification=mU3ta-ZJga-aCNg7IlaRaGYK9sDOMagHRNGVW1FSJGE
TXT 16yandex-verification
TXT 17MS=ms14343235

SOA (Start of Authority)

Primary NSns5-65.akam.net
Hostmasterhostmaster.mozilla.com
Serial2024020757
Refresh180s
Retry180s
Expire1209600s
Min TTL60s

More lookups for mozilla.org

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