`aws-redshift.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}
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}
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}
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}
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 #6

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

Same first word

aws-redshift.com

DNS History

9 records (8 active, 1 former)

●NSns1.markmonitor.com2015-05-27 → 2026-07-15 · 2 obs

● 2015-05-27 20:30:40
● 2026-07-15 03:31:34

●NSns2.markmonitor.com2015-05-27 → 2026-07-15 · 2 obs

● 2015-05-27 20:30:40
● 2026-07-15 03:31:34

●NSns3.markmonitor.com2015-05-27 → 2026-07-15 · 2 obs

● 2015-05-27 20:30:40
● 2026-07-15 03:31:34

●NSns4.markmonitor.com2015-05-27 → 2026-07-15 · 2 obs

● 2015-05-27 20:30:40
● 2026-07-15 03:31:34

●NSns5.markmonitor.com2015-05-27 → 2026-07-15 · 2 obs

● 2015-05-27 20:30:40
● 2026-07-15 03:31:34

●NSns6.markmonitor.com2015-05-27 → 2026-07-15 · 2 obs

● 2015-05-27 20:30:40
● 2026-07-15 03:31:34

●NSns7.markmonitor.com2015-05-27 → 2026-07-15 · 2 obs

● 2015-05-27 20:30:40
● 2026-07-15 03:31:34

●A3.33.139.322026-03-09 → 2026-07-15 · 3 obs

○ 2017-03-25 21:10:22
● 2026-03-09 16:58:32
● 2026-07-15 03:31:34

○A72.52.10.142015-05-27 → 2017-03-25 · 4 obs

● 2015-05-27 20:30:40
● 2017-03-25 21:10:22
○ 2026-03-09 16:58:32
○ 2026-07-15 03:31:34

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	l.gtld-servers.net, j.gtld-servers.net, h.gtld-servers.net, d.gtld-servers.net...	-
aws-redshift.com	ns1.markmonitor.com, ns3.markmonitor.com, ns4.markmonitor.com, ns5.markmonitor.com	8 records

✅ Authoritative Response

Server:149.112.160.2

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

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for aws-redshift.com (unsigned zone)

⏱️ Timing

Total: 504ms | 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

aws-redshift.com has exactly one IP address — 3.33.139.32.

mozdeveloper.org, sfo.as53922.stumbleupon.net, fridaynighttripleplay.com plus two other host names have IP numbers in common with aws-redshift.com.

Name Servers

aws-redshift.com delegates authority to 7 name servers: ns1.markmonitor.com, ns2.markmonitor.com, ns3.markmonitor.com plus 4 other.

aws-redshift.com partially shares its NS delegation with several other domains, including aicpa.sg, cbs5localadnetwork.com, paypalgifts.net and two others.

The name servers ns4.markmonitor.com, ns5.markmonitor.com, ns6.markmonitor.com and ns7.markmonitor.com are often found in use alongside these name servers.

Host names pointing to two IP addresses:

ns1.markmonitor.com directs traffic to 149.112.160.1 and 2620:10a:80a8::1.

ns2.markmonitor.com directs traffic to 176.97.158.1 and 2001:67c:10b8::1.

ns3.markmonitor.com directs traffic to 149.112.161.1 and 2620:10a:80a9::1.

ns4.markmonitor.com directs traffic to 192.174.68.1 and 2001:67c:1bc::1.

ns5.markmonitor.com directs traffic to 149.112.160.2 and 2620:10a:80a8::2.

ns6.markmonitor.com directs traffic to 176.97.158.3 and 2001:67c:10b8::3.

ns7.markmonitor.com directs traffic to 149.112.161.2 and 2620:10a:80a9::2.