`alexa-amazon.com`

DNSSEC	⚠️ Not signed
A	3.33.139.32^{🇺🇸 Amazon3.33.128.0/20}
		PTR	`aeedc42b70c898c66.awsglobalaccelerator.com`
NS	`ns1.markmonitor.com` ⭐
		A	2620:10a:80a8::1^{🇨🇦 CIRA-22620:10a:80a8::/48 markmonitor v6 cloud1 979 Bank Street, Suite 400 Ottawa ON K1S 5K5 Canada}
		A	149.112.160.1^{🇨🇦 CIRA-2149.112.160.0/24 markmonitor v4 cloud1 979 Bank Street, Suite 400 Ottawa ON K1S 5K5 Canada}
			PTR	`ip-149-112-160-1.defastlink.net`
NS	`ns2.markmonitor.com` ⚠️ Not in parent delegation
		A	2001:67c:10b8::1^{🇨🇭 RCODEZERO-ANYCAST-SEC22001:67c:10b8::/48 IPCOM-anycast-net}
			PTR	`ns2.markmonitor.com`
		A	176.97.158.1^{🇦🇹 RCODEZERO-ANYCAST-SEC2176.97.158.0/24 NICat-anycast-net}
			PTR	`ns2.markmonitor.com`
NS	`ns3.markmonitor.com`
		A	2620:10a:80a9::1^{🇨🇦 CIRA-32620:10a:80a9::/48 markmonitor v6 cloud2 979 Bank Street, Suite 400 Ottawa ON K1S 5K5 Canada}
		A	149.112.161.1^{🇨🇦 CIRA-3149.112.161.0/24 markmonitor v4 cloud2 979 Bank Street, Suite 400 Ottawa ON K1S 5K5 Canada}
			PTR	`ip-149-112-161-1.defastlink.net`
NS	`ns4.markmonitor.com`
		A	2001:67c:1bc::1^{🇦🇹 RCODEZERO-ANYCAST-SEC1-TLD2001:67c:1bc::/48 IPCom-NET Anycast}
			PTR	`ns1.markmonitor.com`
		A	192.174.68.1^{🇦🇹 RCODEZERO-ANYCAST-SEC1-TLD192.174.68.0/24 NICat-anycast-net}
			PTR	`ns1.markmonitor.com`
NS	`ns5.markmonitor.com`
		A	2620:10a:80a8::2^{🇨🇦 CIRA-22620:10a:80a8::/48 markmonitor v6 cloud1 979 Bank Street, Suite 400 Ottawa ON K1S 5K5 Canada}
		A	149.112.160.2^{🇨🇦 CIRA-2149.112.160.0/24 markmonitor v4 cloud1 979 Bank Street, Suite 400 Ottawa ON K1S 5K5 Canada}
			PTR	`ip-149-112-160-2.defastlink.net`
NS	`ns6.markmonitor.com` ⚠️ Not in parent delegation
		A	2001:67c:10b8::3^{🇨🇭 RCODEZERO-ANYCAST-SEC22001:67c:10b8::/48 IPCOM-anycast-net}
			PTR	`ns6.markmonitor.com`
		A	176.97.158.3^{🇦🇹 RCODEZERO-ANYCAST-SEC2176.97.158.0/24 NICat-anycast-net}
			PTR	`ns6.markmonitor.com`
NS	`ns7.markmonitor.com` ⚠️ Not in parent delegation
		A	2620:10a:80a9::2^{🇨🇦 CIRA-32620:10a:80a9::/48 markmonitor v6 cloud2 979 Bank Street, Suite 400 Ottawa ON K1S 5K5 Canada}
		A	149.112.161.2^{🇨🇦 CIRA-3149.112.161.0/24 markmonitor v4 cloud2 979 Bank Street, Suite 400 Ottawa ON K1S 5K5 Canada}
			PTR	`ip-149-112-161-2.defastlink.net`
TXT	`v=spf1 include:amazon.com -all`
TXT	`spf2.0/pra include:amazon.com -all`
SOA	`ns1.markmonitor.com`hostmaster@markmonitor.com 2018-09-19 #7

`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

alexa-amazon.com

Similar names

amazon-alexa.jp

DNS History

9 records (8 active, 1 former)

●NSns1.markmonitor.com2016-03-06 → 2026-03-22 · 2 obs

● 2016-03-06 04:02:30
● 2026-03-22 22:15:20

●NSns2.markmonitor.com2016-03-06 → 2026-03-22 · 2 obs

● 2016-03-06 04:02:30
● 2026-03-22 22:15:20

●NSns3.markmonitor.com2016-03-06 → 2026-03-22 · 2 obs

● 2016-03-06 04:02:30
● 2026-03-22 22:15:20

●NSns4.markmonitor.com2016-03-06 → 2026-03-22 · 2 obs

● 2016-03-06 04:02:30
● 2026-03-22 22:15:20

●NSns5.markmonitor.com2016-03-06 → 2026-03-22 · 2 obs

● 2016-03-06 04:02:30
● 2026-03-22 22:15:20

●NSns6.markmonitor.com2016-03-06 → 2026-03-22 · 2 obs

● 2016-03-06 04:02:30
● 2026-03-22 22:15:20

●NSns7.markmonitor.com2016-03-06 → 2026-03-22 · 2 obs

● 2016-03-06 04:02:30
● 2026-03-22 22:15:20

●A3.33.139.322026-02-19 → 2026-03-22 · 3 obs

○ 2020-01-23 07:27:34
● 2026-02-19 15:06:12
● 2026-03-22 22:15:20

○A72.52.10.142016-03-06 → 2020-01-23 · 4 obs

● 2016-03-06 04:02:30
● 2020-01-23 07:27:34
○ 2026-02-19 15:06:12
○ 2026-03-22 22:15:20

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	b.gtld-servers.net, d.gtld-servers.net, k.gtld-servers.net, l.gtld-servers.net...	-
alexa-amazon.com	ns1.markmonitor.com, ns3.markmonitor.com, ns4.markmonitor.com, ns5.markmonitor.com	8 records

✅ Authoritative Response

Server: 192.174.68.1

NS records: ns1.markmonitor.com, ns3.markmonitor.com, ns4.markmonitor.com, ns5.markmonitor.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for alexa-amazon.com (unsigned zone)

⏱️ Timing

Total: 437ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`3.33.139.32`
NS	7	`ns1.markmonitor.com, ns2.markmonitor.com...`
TXT	2	`v=spf1 include:amazon.com -all, spf2.0/pra include:amazon.com -all`
SOA	1	`ns1.markmonitor.com hostmaster.markmonit`

📌 Glue Records Collected

Total: 8

Out-of-bailiwick: 8 (ns1.markmonitor.com, ns1.markmonitor.com, ns3.markmonitor.com...)

Analysis

IP Addresses

alexa-amazon.com points to a single IP number: 3.33.139.32.

other host names for instance filehippo.directory, overwatchgame.com, lyftfare.com, lawinfolatino.com and intheknow.be share IP numbers with alexa-amazon.com.

Name Servers

alexa-amazon.com is delegated to seven name servers: ns1.markmonitor.com, ns2.markmonitor.com, ns3.markmonitor.com, ns4.markmonitor.com, ns5.markmonitor.com, ns6.markmonitor.com and ns7.markmonitor.com.

alexa-amazon.com at least partially shares name servers with other domains, for instance fgroupon.com, cvshezalth.com, biofreeze.co.uk, bet365.irish and kenner.de.