claimsetup.com - dns.ninja

`claimsetup.com`

DNSSEC	⚠️ Not signed
NS	`ns1-05.azure-dns.com` ⭐ ⚠️ Not in parent delegation
		A	2603:1061:0:700::5^{🇺🇸 Microsoft2603:1000::/25 MICROSOFT}
			PTR	`ns1-05.azure-dns.com`
		A	13.107.236.5^{🇺🇸 Microsoft13.104.0.0/14 MICROSOFT}
NS	`ns-551.awsdns-04.net` ⚠️ Not in zone NS records
		A	2600:9000:5302:2700::1^{🇺🇸 Amazon2600:9000:5302::/48 - CloudFront}
			PTR	`ns-551.awsdns-04.net`
		A	205.251.194.39^{🇺🇸 Amazon205.251.194.0/24 prefix}
			PTR	`ns-551.awsdns-04.net`
NS	`ns2-05.azure-dns.net`
		A	2620:1ec:8ec:700::5^{🇺🇸 Microsoft2620:1ec::/36 MICROSOFT}
			PTR	`ns2-05.azure-dns.net`
		A	150.171.21.5^{🇺🇸 Microsoft150.171.0.0/16 MICROSOFT}
NS	`ns3-05.azure-dns.org`
		A	2a01:111:4000:700::5^{🇬🇧 Microsoft2a01:111:4000::/36}
			PTR	`ns3-05.azure-dns.org`
		A	204.14.183.5^{🇺🇸 Microsoft204.14.180.0/22}
NS	`ns4-05.azure-dns.info`
		A	2620:1ec:bda:700::5^{🇺🇸 Microsoft2620:1ec::/36 MICROSOFT}
			PTR	`ns4-05.azure-dns.info`
		A	208.84.5.5^{🇺🇸 Microsoft208.84.0.0/21 MICROSOFT}
MX	`inbound-smtp.us-east-1.amazonaws.com` ⭐
		A	3.211.210.226^{🇺🇸 Amazon3.208.0.0/12 EC2 IAD prefix}
		A	44.206.9.87^{🇺🇸 Amazon44.192.0.0/11 EC2 IAD prefix}
		A	44.210.166.32^{🇺🇸 Amazon44.192.0.0/11 EC2 IAD prefix}
		A	54.164.173.191^{🇺🇸 Amazon54.164.0.0/15 EC2 IAD prefix}
		A	54.197.5.236^{🇺🇸 Amazon54.196.0.0/15 EC2 IAD 54.196.0.0/15}
TXT	`v=spf1 -all`
SOA	`ns1-05.azure-dns.com`azuredns-hostmaster@microsoft.com serial=1

`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=1782683370

Same first word

claimsetup.com

Similar names

DNS History

9 records (6 active, 3 former)

○NSns-1214.awsdns-23.org2016-12-19 → 2026-03-28 · 4 obs

● 2016-12-19 14:28:42
● 2026-03-28 02:27:12
○ 2026-04-10 23:05:56
○ 2026-06-28 22:18:10

○NSns-2042.awsdns-63.co.uk2016-12-19 → 2026-03-28 · 4 obs

● 2016-12-19 14:28:42
● 2026-03-28 02:27:12
○ 2026-04-10 23:05:56
○ 2026-06-28 22:18:10

○NSns-360.awsdns-45.com2016-12-19 → 2026-04-10 · 4 obs

● 2016-12-19 14:28:42
● 2026-04-10 23:05:56
○ 2026-06-21 13:16:04
○ 2026-06-28 22:18:10

●NSns-551.awsdns-04.net2016-12-19 → 2026-06-28 · 2 obs

● 2016-12-19 14:28:42
● 2026-06-28 22:18:10

●NSns1-05.azure-dns.com2026-03-28 → 2026-06-28 · 3 obs

○ 2016-12-19 14:28:42
● 2026-03-28 02:27:12
● 2026-06-28 22:18:10

●NSns2-05.azure-dns.net2026-03-28 → 2026-06-28 · 3 obs

○ 2016-12-19 14:28:42
● 2026-03-28 02:27:12
● 2026-06-28 22:18:10

●NSns3-05.azure-dns.org2026-03-28 → 2026-06-28 · 3 obs

○ 2016-12-19 14:28:42
● 2026-03-28 02:27:12
● 2026-06-28 22:18:10

●NSns4-05.azure-dns.info2026-03-28 → 2026-06-28 · 3 obs

○ 2016-12-19 14:28:42
● 2026-03-28 02:27:12
● 2026-06-28 22:18:10

●MXinbound-smtp.us-east-1.amazonaws.com2016-12-19 → 2026-06-28 · 2 obs

● 2016-12-19 14:28:42
● 2026-06-28 22:18:10

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	l.gtld-servers.net, j.gtld-servers.net, h.gtld-servers.net, d.gtld-servers.net...	-
claimsetup.com	ns-551.awsdns-04.net, ns2-05.azure-dns.net, ns3-05.azure-dns.org, ns4-05.azure-dns.info	-

✅ Authoritative Response

Server:204.14.183.5

NS records: ns-551.awsdns-04.net, ns2-05.azure-dns.net, ns3-05.azure-dns.org, ns4-05.azure-dns.info

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for claimsetup.com (unsigned zone)

⏱️ Timing

Total: 375ms | Queries: -

📄 Records

Type	Count	Sample Data
NS	4	`ns1-05.azure-dns.com, ns2-05.azure-dns.net...`
MX	1	`inbound-smtp.us-east-1.amazonaws.com (pr`
TXT	1	`v=spf1 -all`
SOA	1	`ns1-05.azure-dns.com azuredns-hostmaster`

Analysis

Name Servers

The authoritative name servers for claimsetup.com are ns1-05.azure-dns.com, ns4-05.azure-dns.info, ns-551.awsdns-04.net and two others.

claimsetup.com shares at least some of its name servers with other domains, including zonal.cloud, penponds.com, tissotshop.com.ru and two others.

These name servers are frequently paired with the name servers ns2-05.azure-dns.net and ns3-05.azure-dns.org.

Hosts with two IP numbers each:

ns1-05.azure-dns.com resolves to two addresses: 13.107.236.5 and 2603:1061:0:700::5.

ns4-05.azure-dns.info resolves to two addresses: 208.84.5.5 and 2620:1ec:bda:700::5.

ns-551.awsdns-04.net resolves to two addresses: 205.251.194.39 and 2600:9000:5302:2700::1.

ns2-05.azure-dns.net resolves to two addresses: 150.171.21.5 and 2620:1ec:8ec:700::5.

ns3-05.azure-dns.org resolves to two addresses: 204.14.183.5 and 2a01:111:4000:700::5.

Mail Servers

claimsetup.com routes its mail through a single mail server, inbound-smtp.us-east-1.amazonaws.com.

claimsetup.com has the same mail server arrangement as a number of other domains, for example cirrusops.slack.com, wotcdigitalpublishing.slack.com, secureflag.slack.com and two more.

claimsetup.com shares at least some of its mail servers with other domains — for example robinson-cole.atlassian.net, navdyhud.atlassian.net, connectiverx.atlassian.net and two more.

It is common to find these mail servers paired with the mail servers inbound-smtp.us-west-2.amazonaws.com.

inbound-smtp.us-east-1.amazonaws.com resolves to five IP numbers: 3.211.210.226, 44.206.9.87, 44.210.166.32 and two others.