`midnightwest.com`

DNSSEC	⚠️ Not signed
A	54.159.98.68^{🇺🇸 Amazon54.156.0.0/14 EC2 IAD prefix}
		PTR	`ec2-54-159-98-68.compute-1.amazonaws.com`
NS	`ns05.domaincontrol.com` ⭐
		A	2603:5:2160::3^{🇺🇸 GODADDY-DNS2603:5:2160::/44}
			PTR	`ns05.domaincontrol.com`
		A	97.74.102.3^{🇺🇸 GODADDY-DNS97.74.102.0/23}
			PTR	`ns05.domaincontrol.com`
NS	`ns06.domaincontrol.com`
		A	2603:5:2260::3^{🇺🇸 GODADDY-DNS2603:5:2260::/44}
			PTR	`ns06.domaincontrol.com`
		A	173.201.70.3^{🇺🇸 GODADDY-DNS173.201.70.0/23}
			PTR	`ns06.domaincontrol.com`
SOA	`ns05.domaincontrol.com`dns@jomax.net 2020-10-21 #2

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

Previously MX for

midnightwest.com

Same first word

midnightwest.com

DNS History

8 records (3 active, 5 former)

●NSns05.domaincontrol.com2020-03-29 → 2026-03-27 · 3 obs

○ 2017-02-19 20:53:38
● 2020-03-29 15:31:40
● 2026-03-27 16:07:10

●NSns06.domaincontrol.com2020-03-29 → 2026-03-27 · 3 obs

○ 2017-02-19 20:53:38
● 2020-03-29 15:31:40
● 2026-03-27 16:07:10

○NSns1.starfish.arvixe.com2016-03-15 → 2016-07-09 · 4 obs

● 2016-03-15 21:45:22
● 2016-07-09 18:38:38
○ 2017-02-19 20:53:38
○ 2026-03-27 16:07:10

○NSns2.starfish.arvixe.com2016-03-15 → 2016-07-09 · 4 obs

● 2016-03-15 21:45:22
● 2016-07-09 18:38:38
○ 2017-02-19 20:53:38
○ 2026-03-27 16:07:10

○MXmidnightwest.com2016-03-15 → 2016-07-09 · 4 obs

● 2016-03-15 21:45:22
● 2016-07-09 18:38:38
○ 2017-02-19 20:53:38
○ 2026-03-27 16:07:10

○A198.252.65.42016-03-15 → 2016-07-09 · 4 obs

● 2016-03-15 21:45:22
● 2016-07-09 18:38:38
○ 2017-02-19 20:53:38
○ 2026-03-27 16:07:10

●A54.159.98.682026-02-25 → 2026-03-27 · 3 obs

○ 2020-03-29 15:31:40
● 2026-02-25 10:40:20
● 2026-03-27 16:07:10

○A69.175.14.752020-03-29 → 2020-03-29 · 4 obs

○ 2017-02-19 20:53:38
● 2020-03-29 15:31:40
○ 2026-02-25 10:40:20
○ 2026-03-27 16:07:10

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net...	-
midnightwest.com	ns05.domaincontrol.com, ns06.domaincontrol.com	4 records

✅ Authoritative Response

Server:97.74.102.3

NS records: ns05.domaincontrol.com, ns06.domaincontrol.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for midnightwest.com (unsigned zone)

⏱️ Timing

Total: 76ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`54.159.98.68`
NS	2	`ns05.domaincontrol.com, ns06.domaincontrol.com`
SOA	1	`ns05.domaincontrol.com dns.jomax.net`

📌 Glue Records Collected

Total: 4

Out-of-bailiwick: 4 (ns05.domaincontrol.com, ns05.domaincontrol.com, ns06.domaincontrol.com...)

Analysis

IP Addresses

midnightwest.com points to a single IP number: 54.159.98.68.

Other host names, for instance sbex.com, aaz.com, keuno.com, zenafa.com and rosealyn.com share IP numbers with midnightwest.com.

Name Servers

midnightwest.com is delegated to two name servers: ns05.domaincontrol.com and ns06.domaincontrol.com.

midnightwest.com uses the same name server setup as other domains, for instance niaoren001.com, ninesoptic.com, teamblue.ca, rioscigars.com and fredsautoremoval.com.

midnightwest.com partially shares name servers with other domains, for instance pmabogados.co.

Host names with two IP numbers:

The host ns05.domaincontrol.com points to 2603:5:2160::3 and 97.74.102.3.

The host ns06.domaincontrol.com points to 2603:5:2260::3 and 173.201.70.3.

midnightwest.com - robtex.com