`amazondefence.com`

DNSSEC	⚠️ Not signed
A	162.255.119.30^{🇺🇸 NAMCHEAP-PH162.255.119.0/24 Namecheap, Inc. 11400 W. Olympic Blvd. Suite 200 Los Angeles, CA 90064 UNITED STATES}
NS	`dns1.registrar-servers.com` ⭐
		A	2610:a1:1024::200^{🇺🇸 MAINT-ID-120082610:a1:1024::/48 Neustar}
			PTR	`dns1.namecheaphosting.com`
			PTR	`dns1.registrar-servers.com`
		A	156.154.132.200^{🇺🇸 MAINT-ID-12008156.154.132.0/24 Neustar}
			PTR	`dns1.namecheaphosting.com`
			PTR	`dns1.registrar-servers.com`
NS	`dns2.registrar-servers.com`
		A	2610:a1:1025::200^{🇺🇸 MAINT-ID-120082610:a1:1025::/48 Neustar}
			PTR	`dns2.namecheaphosting.com`
			PTR	`dns2.registrar-servers.com`
		A	156.154.133.200^{🇺🇸 MAINT-ID-12008156.154.133.0/24 Neustar}
			PTR	`ip-156-154-133-200.defastlink.net`
MX	`aspmx.l.google.com` ⭐
		A	2607:f8b0:4023:c03::1b^{🇺🇸 Google2607:f8b0::/32}
			PTR	`dy-in-f27.1e100.net`
		A	142.250.141.27^{🇺🇸 Google142.250.141.0/24}
			PTR	`dd-in-f27.1e100.net`
MX	`alt1.aspmx.l.google.com`⁽⁵⁾
		A	2800:3f0:4003:c0f::1a^{🇨🇱 Google2800:3f0:4003::/48}
		A	108.177.123.27^{🇺🇸 Google108.177.123.0/24}
			PTR	`lcscld-in-f27.1e100.net`
MX	`alt2.aspmx.l.google.com`⁽⁵⁾
		A	2607:f8b0:4023:1015::1b^{🇺🇸 Google2607:f8b0::/32}
			PTR	`yudfwta-in-f27.1e100.net`
		A	172.253.135.27^{🇺🇸 Google172.253.135.0/24}
			PTR	`yudfwta-in-f27.1e100.net`
MX	`aspmx2.googlemail.com`⁽¹⁰⁾
		A	2607:f8b0:4023:2801::1a^{🇺🇸 Google2607:f8b0::/32}
			PTR	`lcausi-in-f26.1e100.net`
		A	192.178.128.27^{🇺🇸 Google192.178.128.0/24}
			PTR	`lcausi-in-f27.1e100.net`
MX	`aspmx3.googlemail.com`⁽¹⁰⁾
		A	2a00:1450:400b:c02::1a^{🇮🇪 Google2a00:1450:400b::/48}
			PTR	`dj-in-f26.1e100.net`
		A	172.253.116.26^{🇺🇸 Google172.253.116.0/24}
			PTR	`dj-in-f26.1e100.net`
SOA	`dns1.registrar-servers.com`hostmaster@registrar-servers.com serial=1761149039

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

Same first word

amazondefence.com

DNS History

12 records (8 active, 4 former)

●NSdns1.registrar-servers.com2026-02-16 → 2026-03-28 · 3 obs

○ 2018-09-04 22:36:58
● 2026-02-16 22:21:36
● 2026-03-28 01:10:32

●NSdns2.registrar-servers.com2026-02-16 → 2026-03-28 · 3 obs

○ 2018-09-04 22:36:58
● 2026-02-16 22:21:36
● 2026-03-28 01:10:32

○NSns129.ehosts.com2016-12-14 → 2018-09-04 · 4 obs

● 2016-12-14 14:51:28
● 2018-09-04 22:36:58
○ 2026-02-16 22:21:36
○ 2026-03-28 01:10:32

○NSns130.ehosts.com2016-12-14 → 2018-09-04 · 4 obs

● 2016-12-14 14:51:28
● 2018-09-04 22:36:58
○ 2026-02-16 22:21:36
○ 2026-03-28 01:10:32

●MXalt1.aspmx.l.google.com2026-02-16 → 2026-03-28 · 3 obs

○ 2018-09-04 22:36:58
● 2026-02-16 22:21:36
● 2026-03-28 01:10:32

●MXalt2.aspmx.l.google.com2026-02-16 → 2026-03-28 · 3 obs

○ 2018-09-04 22:36:58
● 2026-02-16 22:21:36
● 2026-03-28 01:10:32

●MXaspmx.l.google.com2026-02-16 → 2026-03-28 · 3 obs

○ 2018-09-04 22:36:58
● 2026-02-16 22:21:36
● 2026-03-28 01:10:32

●MXaspmx2.googlemail.com2026-02-16 → 2026-03-28 · 3 obs

○ 2018-09-04 22:36:58
● 2026-02-16 22:21:36
● 2026-03-28 01:10:32

●MXaspmx3.googlemail.com2026-02-16 → 2026-03-28 · 3 obs

○ 2018-09-04 22:36:58
● 2026-02-16 22:21:36
● 2026-03-28 01:10:32

○MXmail.amazondefence.com2016-12-14 → 2018-09-04 · 4 obs

● 2016-12-14 14:51:28
● 2018-09-04 22:36:58
○ 2026-02-16 22:21:36
○ 2026-03-28 01:10:32

○A108.167.160.902016-12-14 → 2018-09-04 · 4 obs

● 2016-12-14 14:51:28
● 2018-09-04 22:36:58
○ 2026-02-16 22:21:36
○ 2026-03-28 01:10:32

●A162.255.119.302026-02-16 → 2026-03-28 · 3 obs

○ 2018-09-04 22:36:58
● 2026-02-16 22:21:36
● 2026-03-28 01:10:32

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	c.gtld-servers.net, e.gtld-servers.net, g.gtld-servers.net, b.gtld-servers.net...	-
amazondefence.com	dns1.registrar-servers.com, dns2.registrar-servers.com	4 records

✅ Authoritative Response

Server:156.154.132.200

NS records: dns1.registrar-servers.com, dns2.registrar-servers.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for amazondefence.com (unsigned zone)

⏱️ Timing

Total: 167ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`162.255.119.30`
NS	2	`dns1.registrar-servers.com, dns2.registrar-servers.com`
MX	5	`aspmx.l.google.com (pri: 1), alt1.aspmx.l.google.com (pri: 5)...`
SOA	1	`dns1.registrar-servers.com hostmaster.re`

📌 Glue Records Collected

Total: 4

Out-of-bailiwick: 4 (dns1.registrar-servers.com, dns1.registrar-servers.com, dns2.registrar-servers.com...)

Analysis

IP Addresses

amazondefence.com points to a single IP: 162.255.119.30.

Other host names, for instance cobalt-innovations.com, cif2020.biz, blinktopay.com, (0x6e756465)mermaids.com and lesserrors.com share IP numbers with amazondefence.com.

Name Servers

Two name servers dns1.registrar-servers.com and dns2.registrar-servers.com handle delegation for amazondefence.com.

amazondefence.com uses the same name server setup as other domains, for example 2kwords.com, nyackacupuncture.com, braii.org, mainpac.org and deleteme.org.

amazondefence.com shares name servers with other domains at least partially, for instance xn--lafranaise-g4a4g.com, quantumcomputingexplained.net and incadi.org.

These name servers are commonly used with dns3.registrar-servers.com, dns4.registrar-servers.com and dns5.registrar-servers.com.

Host names with two IP numbers:

dns1.registrar-servers.com points to: 2610:a1:1024::200 and 156.154.132.200

dns2.registrar-servers.com points to: 2610:a1:1025::200 and 156.154.133.200