`nullmx.thaiangle.com`

DNSSEC	⚠️ Not signed
NS	`ns1.dns-redirect.com` ⭐ ⚠️ Not in parent delegation
		A	5.161.47.86^{🇺🇸 HETZNER-CLOUD2-AS5.161.47.0/24}
			PTR	`static.86.47.161.5.clients.your-server.de`
		A	5.161.230.87^{🇺🇸 HETZNER-CLOUD2-AS5.161.230.0/24}
			PTR	`static.87.230.161.5.clients.your-server.de`
		A	195.201.128.179^{🇩🇪 Hetzner195.201.0.0/16 HETZNER-DC}
			PTR	`static.179.128.201.195.clients.your-server.de`
NS	`ns2.dns-redirect.com` ⚠️ Not in parent delegation
		A	76.223.91.20^{🇺🇸 Amazon76.223.80.0/20}
			PTR	`ad988eeb126877ff9.awsglobalaccelerator.com`
		A	166.117.68.124^{🇺🇸 Amazon166.117.64.0/20}
			PTR	`ad988eeb126877ff9.awsglobalaccelerator.com`
SOA	`ns1.dns-redirect.com`admin@dns.com 2024-07-29 #1

`thaiangle.com`

	DNSSEC	⚠️ Not signed
	A	2406:da1e:214:c901:714b:5e6b:769c:15e6^{🇨🇳 Amazon2406:da1e::/38}
	A	2600:1f18:6a07:601:3a2e:6474:85a2:7d3b^{🇺🇸 Amazon2600:1f18:6000::/35 AMAZON EC2 IAD prefix}
	A	2600:1f1c:6db:8800:3e4c:7275:7812:f1d8^{🇺🇸 Amazon2600:1f1c:400::/38 AMAZON AWS}
	A	2a01:4f8:1c1e:d6f1::1^{🇩🇪 Hetzner2a01:4f8::/32 HETZNER-IPv6-BLK}
	A	2a01:4ff:f0:5f41::1^{🇺🇸 HETZNER-CLOUD2-AS2a01:4ff::/40 HETZNER-IPv6-BLK}
	A	2a01:4ff:f0:a884::1^{🇺🇸 HETZNER-CLOUD2-AS2a01:4ff::/40 HETZNER-IPv6-BLK}
	A	2a01:4ff:1f0:dd50::1^{🇩🇪 HETZNER-CLOUD3-AS2a01:4ff:100::/40 HETZNER-IPv6-BLK}
	A	2a05:d018:1d22:801:67b1:bfb4:295a:bcf4^{🇮🇪 Amazon2a05:d018:1000::/36 EC2 DUB Prefix}
	A	5.78.156.59^{🇺🇸 HETZNER-CLOUD3-AS5.78.156.0/24}
	A	5.161.47.86^{🇺🇸 HETZNER-CLOUD2-AS5.161.47.0/24}
	A	5.161.230.87^{🇺🇸 HETZNER-CLOUD2-AS5.161.230.0/24}
	A	195.201.128.179^{🇩🇪 Hetzner195.201.0.0/16 HETZNER-DC}
	NS	`ns1.dns-redirect.com` ⭐
	NS	`ns2.dns-redirect.com`
	TXT	`afternic-verification-aGHTsEA2nLa7KRqzmJySAx`
	TXT	`95b3a950-315c-45b8-937a-b865ebeb043a`
	TXT	`abuse-report=mailto:abuse@redirhub.com`
	SOA	`ns1.dns-redirect.com`admin@dns.com 2024-07-29 #1

Same first word

nullmx.net

nullmx.org

nullmx.com

DNS History

4 records (2 active, 2 former)

●NSns1.dns-redirect.com2026-03-16 → 2026-07-19 · 2 obs

● 2026-03-16 00:41:24
● 2026-07-19 20:37:58

●NSns2.dns-redirect.com2026-03-16 → 2026-07-19 · 2 obs

● 2026-03-16 00:41:24
● 2026-07-19 20:37:58

○A209.181.247.1052008-03-17 → 2008-03-17 · 3 obs

● 2008-03-17 08:12:30
○ 2015-10-21 09:03:08
○ 2026-07-19 20:37:58

○A74.220.199.92016-03-20 → 2016-03-20 · 4 obs

○ 2015-10-21 09:03:08
● 2016-03-20 08:05:10
○ 2026-03-16 00:41:24
○ 2026-07-19 20:37:58

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net...	-
thaiangle.com	ns1.dns-redirect.com, ns2.dns-redirect.com	5 records

✅ Authoritative Response

Server:166.117.68.124

NS records: ns1.dns-redirect.com, ns2.dns-redirect.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for thaiangle.com (unsigned zone)

⏱️ Timing

Total: 276ms | Queries: -

📄 Records

Type	Count	Sample Data
NS	2	`ns1.dns-redirect.com, ns2.dns-redirect.com`
SOA	1	`ns1.dns-redirect.com admin.dns.com`

📌 Glue Records Collected

Total: 5

Out-of-bailiwick: 5 (ns1.dns-redirect.com, ns1.dns-redirect.com, ns1.dns-redirect.com...)

Analysis

Name Servers

nullmx.thaiangle.com is served by two delegated name servers, ns1.dns-redirect.com and ns2.dns-redirect.com.

The name server configuration of nullmx.thaiangle.com is shared with other domains, for instance maidservicesoforlando.com, 24-70.com, campquake.com and two others.

Host names carrying three IP numbers:

ns1.dns-redirect.com resolves to three addresses: 5.161.47.86, 5.161.230.87 and 195.201.128.179.

Host names pointing to two IP addresses:

ns2.dns-redirect.com maps to two IP addresses — 76.223.91.20 and 166.117.68.124.

nullmx.thaiangle.com - robtex.com