`pwcchallenge.com`

DNSSEC	⚠️ Not signed
A	173.203.158.10^{🇺🇸 RACKSPACE-IAD173.203.128.0/18 Rackspace Managed Hosting, 9725 Data point drive, Suite 100, San Antonio, TX 78229}
		PTR	`pwcchallenge.com`
NS	`ns1-01.azure-dns.com` ⭐
		A	2603:1061:0:700::1^{🇺🇸 Microsoft2603:1000::/25 MICROSOFT}
			PTR	`ns1-01.azure-dns.com`
		A	13.107.236.1^{🇺🇸 Microsoft13.104.0.0/14 MICROSOFT}
			PTR	`ns1-01.azure-dns.com`
NS	`ns2-01.azure-dns.net`
		A	2620:1ec:8ec:700::1^{🇺🇸 Microsoft2620:1ec::/36 MICROSOFT}
			PTR	`ns2-01.azure-dns.net`
		A	150.171.21.1^{🇺🇸 Microsoft150.171.0.0/16 MICROSOFT}
			PTR	`ns2-01.azure-dns.net`
NS	`ns3-01.azure-dns.org`
		A	2a01:111:4000:700::1^{🇬🇧 Microsoft2a01:111:4000::/36}
			PTR	`ns3-01.azure-dns.org`
		A	204.14.183.1^{🇺🇸 Microsoft204.14.180.0/22}
			PTR	`ns3-01.azure-dns.org`
NS	`ns4-01.azure-dns.info`
		A	2620:1ec:bda:700::1^{🇺🇸 Microsoft2620:1ec::/36 MICROSOFT}
			PTR	`ns4-01.azure-dns.info`
		A	208.84.5.1^{🇺🇸 Microsoft208.84.0.0/21 MICROSOFT}
			PTR	`ns4-01.azure-dns.info`
SOA	`ns1-01.azure-dns.com`hostmaster@rackspace.com serial=1411750359

`com`

	DNSSEC	🔒 Signed (DS record present)
	NS	`a.gtld-servers.net` ⭐
	NS	`b.gtld-servers.net`
	NS	`c.gtld-servers.net`
	NS	`d.gtld-servers.net`
	NS	`e.gtld-servers.net`
	NS	`f.gtld-servers.net`
	NS	`g.gtld-servers.net`
	NS	`h.gtld-servers.net`
	NS	`i.gtld-servers.net`
	NS	`j.gtld-servers.net`
	NS	`k.gtld-servers.net`
	NS	`l.gtld-servers.net`
	NS	`m.gtld-servers.net`
	SOA	`a.gtld-servers.net`nstld@verisign-grs.com serial=1771291435

PTR for

10.158.203.173.in-addr.arpa

Same first word

pwcchallenge.com

DNS History

7 records (5 active, 2 former)

○NSns.rackspace.com2015-05-23 → 2017-05-14 · 4 obs

● 2015-05-23 05:38:42
● 2017-05-14 15:39:30
○ 2026-03-24 01:40:24
○ 2026-03-24 01:40:26

●NSns1-01.azure-dns.com2026-03-24 → 2026-03-24 · 3 obs

○ 2017-05-14 15:39:30
● 2026-03-24 01:40:24
● 2026-03-24 01:40:26

●NSns2-01.azure-dns.net2026-03-24 → 2026-03-24 · 3 obs

○ 2017-05-14 15:39:30
● 2026-03-24 01:40:24
● 2026-03-24 01:40:26

○NSns2.rackspace.com2015-05-23 → 2017-05-14 · 4 obs

● 2015-05-23 05:38:42
● 2017-05-14 15:39:30
○ 2026-03-24 01:40:24
○ 2026-03-24 01:40:26

●NSns3-01.azure-dns.org2026-03-24 → 2026-03-24 · 3 obs

○ 2017-05-14 15:39:30
● 2026-03-24 01:40:24
● 2026-03-24 01:40:26

●NSns4-01.azure-dns.info2026-03-24 → 2026-03-24 · 3 obs

○ 2017-05-14 15:39:30
● 2026-03-24 01:40:24
● 2026-03-24 01:40:26

●A173.203.158.102015-05-23 → 2026-03-24 · 2 obs

● 2015-05-23 05:38:42
● 2026-03-24 01:40:26

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	l.gtld-servers.net, j.gtld-servers.net, h.gtld-servers.net, d.gtld-servers.net...	-
pwcchallenge.com	ns1-01.azure-dns.com, ns2-01.azure-dns.net, ns3-01.azure-dns.org, ns4-01.azure-dns.info	2 records

✅ Authoritative Response

Server:13.107.236.1

NS records: ns1-01.azure-dns.com, ns2-01.azure-dns.net, ns3-01.azure-dns.org, ns4-01.azure-dns.info

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for pwcchallenge.com (unsigned zone)

⏱️ Timing

Total: 246ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`173.203.158.10`
NS	4	`ns1-01.azure-dns.com, ns2-01.azure-dns.net...`
SOA	1	`ns1-01.azure-dns.com hostmaster.rackspac`

📌 Glue Records Collected

Total: 2

Out-of-bailiwick: 2 (ns1-01.azure-dns.com, ns1-01.azure-dns.com)

Analysis

IP Addresses

pwcchallenge.com resolves to one IP number: 173.203.158.10.

Name Servers

pwcchallenge.com is delegated to four name servers: ns1-01.azure-dns.com, ns4-01.azure-dns.info, ns2-01.azure-dns.net and ns3-01.azure-dns.org.

pwcchallenge.com at least partially shares name servers with other domains, for instance directcoverinsurance.com, 35.13.20.in-addr.arpa, xn--gmqv3m7qkhxxtnhiua698gqfl.com, odefsey.com and ecat.ie.

Host names with two IP numbers:

ns1-01.azure-dns.com points to 2603:1061:0:700::1 and 13.107.236.1; ns4-01.azure-dns.info points to 2620:1ec:bda:700::1 and 208.84.5.1; ns2-01.azure-dns.net points to 2620:1ec:8ec:700::1 and 150.171.21.1; ns3-01.azure-dns.org points to 2a01:111:4000:700::1 and 204.14.183.1.

pwcchallenge.com - robtex.com