`wecarrytheload.com`

DNSSEC	⚠️ Not signed
NS	`ns1-04.azure-dns.com` ⭐
		A	2603:1061:0:700::4^{🇺🇸 Microsoft2603:1000::/25 MICROSOFT}
			PTR	`ns1-04.azure-dns.com`
		A	13.107.236.4^{🇺🇸 Microsoft13.104.0.0/14 MICROSOFT}
			PTR	`ip-13-107-236-4.defastlink.net`
NS	`ns2-04.azure-dns.net`
		A	2620:1ec:8ec:700::4^{🇺🇸 Microsoft2620:1ec::/36 MICROSOFT}
			PTR	`ns2-04.azure-dns.net`
		A	150.171.21.4^{🇺🇸 Microsoft150.171.0.0/16 MICROSOFT}
			PTR	`ip-150-171-21-4.defastlink.net`
NS	`ns3-04.azure-dns.org`
		A	2a01:111:4000:700::4^{🇬🇧 Microsoft2a01:111:4000::/36}
			PTR	`ns3-04.azure-dns.org`
		A	204.14.183.4^{🇺🇸 Microsoft204.14.180.0/22}
			PTR	`ip-204-14-183-4.defastlink.net`
NS	`ns4-04.azure-dns.info`
		A	2620:1ec:bda:700::4^{🇺🇸 Microsoft2620:1ec::/36 MICROSOFT}
			PTR	`ns4-04.azure-dns.info`
		A	208.84.5.4^{🇺🇸 Microsoft208.84.0.0/21 MICROSOFT}
			PTR	`ip-208-84-5-4.defastlink.net`
TXT	`v=spf1 -all`
SOA	`ns1-04.azure-dns.com`hostmaster@sirva.com 2004-08-04 #30

`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

Same first word

wecarrytheload.com

DNS History

7 records (4 active, 3 former)

●NSns1-04.azure-dns.com2018-08-07 → 2026-03-23 · 3 obs

○ 2017-01-18 00:28:20
● 2018-08-07 05:22:56
● 2026-03-23 05:05:28

○NSns1.sirva.com2015-05-29 → 2017-01-18 · 4 obs

● 2015-05-29 10:05:48
● 2017-01-18 00:28:20
○ 2018-08-07 05:22:56
○ 2026-03-23 05:05:28

●NSns2-04.azure-dns.net2018-08-07 → 2026-03-23 · 3 obs

○ 2017-01-18 00:28:20
● 2018-08-07 05:22:56
● 2026-03-23 05:05:28

○NSns2.sirva.com2015-05-29 → 2017-01-18 · 4 obs

● 2015-05-29 10:05:48
● 2017-01-18 00:28:20
○ 2018-08-07 05:22:56
○ 2026-03-23 05:05:28

●NSns3-04.azure-dns.org2018-08-07 → 2026-03-23 · 3 obs

○ 2017-01-18 00:28:20
● 2018-08-07 05:22:56
● 2026-03-23 05:05:28

○NSns3.sirva.com2015-05-29 → 2017-01-18 · 4 obs

● 2015-05-29 10:05:48
● 2017-01-18 00:28:20
○ 2018-08-07 05:22:56
○ 2026-03-23 05:05:28

●NSns4-04.azure-dns.info2018-08-07 → 2026-03-23 · 3 obs

○ 2017-01-18 00:28:20
● 2018-08-07 05:22:56
● 2026-03-23 05:05:28

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	g.gtld-servers.net, j.gtld-servers.net, i.gtld-servers.net, h.gtld-servers.net...	-
wecarrytheload.com	ns1-04.azure-dns.com, ns2-04.azure-dns.net, ns3-04.azure-dns.org, ns4-04.azure-dns.info	2 records

✅ Authoritative Response

Server:13.107.236.4

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

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for wecarrytheload.com (unsigned zone)

⏱️ Timing

Total: 698ms | Queries: -

📄 Records

Type	Count	Sample Data
NS	4	`ns1-04.azure-dns.com, ns2-04.azure-dns.net...`
TXT	1	`v=spf1 -all`
SOA	1	`ns1-04.azure-dns.com hostmaster.sirva.co`

📌 Glue Records Collected

Total: 2

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

Analysis

Name Servers

wecarrytheload.com's delegation is handled by four name servers: ns1-04.azure-dns.com, ns4-04.azure-dns.info, ns2-04.azure-dns.net and ns3-04.azure-dns.org.

wecarrytheload.com partially shares name servers with other domains; examples include clamed.com.br, swatch.ru, lifefitness.support, lyncvoicemail.com and powpowmeow.com.

Host names with two IPs:

ns1-04.azure-dns.com points to 2603:1061:0:700::4 and 13.107.236.4

ns4-04.azure-dns.info points to 2620:1ec:bda:700::4 and 208.84.5.4

ns2-04.azure-dns.net points to 2620:1ec:8ec:700::4 and 150.171.21.4

ns3-04.azure-dns.org points to 2a01:111:4000:700::4 and 204.14.183.4

wecarrytheload.com - robtex.com