iPGaze

DNS records for disneyplus.com

disneyplus.com resolves to 1 IPv4 address and 1 IPv6 address, it is served by 8 nameservers (sdns110.ultradns.biz), and accepts mail via 1 MX record.

Run a live lookup ↗

A records (IPv4)

TTL 20s34.110.155.89

AAAA records (IPv6)

TTL 20s2600:1901:0:84f4::80

MX records (mail servers)

Priority 0disneyplus-com.mail.protection.outlook.com

NS records (nameservers)

NS 1sdns110.ultradns.biz
NS 2dns1.p09.nsone.net
NS 3sdns110.ultradns.com
NS 4sdns110.ultradns.org
NS 5dns4.p09.nsone.net
NS 6dns2.p09.nsone.net
NS 7dns3.p09.nsone.net
NS 8sdns110.ultradns.net

TXT records

TXT 1google-site-verification=a1Ohi-qxhRb7UPygwEbRezXXT1afxpg_ArTb4yjbn5I
TXT 2google-site-verification=tDciPfe7Hg7cjsfptEnR_EZH3lL3MSgFZPMfdmYVCNQ
TXT 3MS=ms47955076
TXT 4google-site-verification=__yAZClx1Ojg67WMxmYLYF-UnJc_hXWShKEKIgTe3H8
TXT 5facebook-domain-verification=e5xsar5ewqxqfbavdbut619y111lqe
TXT 6facebook-domain-verification=91zw7nbko3e8gw7b5txf98f1fo0a00
TXT 7_izqn8weuqp05kxgw4djnmhiwshn232z
TXT 8google-site-verification=3rPKcPsgy3_fOFd92rTBFswz4_ktFZozcKrPXPH1014
TXT 9v=spf1 include:spf.protection.outlook.com include:sn-spf.disneyplus.com include:_spf.salesforce.com -all
TXT 10apple-domain-verification=4ugvzepXs8LSLrQrv9_PWk6m4LG9XCbvH6tOS5KwXqk
TXT 11gSc5USVrswRL+qEePvNIjpPMXPr4pK6052giPDip9/Y=
TXT 12google-site-verification=tuk-5kwnhWESiRyD8ZdoNRDrIOyKAvqQps1CXjg6yHg\010
TXT 13google-site-verification=6ZhJ0OE5f7H_A9NN0d3Slo5LdMBREfkYZAoXRx9WC5I
TXT 14google-site-verification=PL2CNSkW90tzzdDqkpbi5uO4OAfXmlt4EHV0SXcx9O0

SOA (Start of Authority)

Primary NSdns1.p09.nsone.net
Hostmasterhostmaster.nsone.net
Serial1656350265
Refresh3600s
Retry600s
Expire604800s
Min TTL3600s

More lookups for disneyplus.com

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