nullmx.mitcafe.com - dns.ninja

`nullmx.mitcafe.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

`mitcafe.com`

	DNSSEC	⚠️ Not signed
	A	2406:da1e:214:c901:a1e2:fc7f:1e14:6ae2^{🇨🇳 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:9250:95cf:fe2:6f04^{🇺🇸 Amazon2600:1f1c:400::/38 AMAZON AWS}
	A	2a01:4f8:1c1e:d6f1::1^{🇩🇪 Hetzner2a01:4f8::/32 HETZNER-IPv6-BLK}
	A	2a01:4f9:c013:29f7::1^{🇩🇪 Hetzner2a01:4f9::/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	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	46.62.237.138^{🇩🇪 Hetzner46.62.128.0/17 HETZNER-DC}
	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

17 records (2 active, 15 former)

○NSbuy.internettraffic.com2015-08-06 → 2016-03-14 · 4 obs

● 2015-08-06 22:30:58
● 2016-03-14 08:18:08
○ 2016-09-23 12:27:20
○ 2026-07-04 08:58:26

●NSns1.dns-redirect.com2026-05-10 → 2026-07-04 · 3 obs

○ 2016-09-23 12:27:20
● 2026-05-10 05:49:02
● 2026-07-04 08:58:26

○NSns1.namebrightdns.com2016-09-23 → 2016-09-23 · 4 obs

○ 2016-03-14 08:18:08
● 2016-09-23 12:27:20
○ 2026-05-10 05:49:02
○ 2026-07-04 08:58:26

○NSns1.uniregistrymarket.link2016-09-23 → 2016-09-23 · 4 obs

○ 2016-03-14 08:18:08
● 2016-09-23 12:27:20
○ 2026-05-10 05:49:02
○ 2026-07-04 08:58:26

●NSns2.dns-redirect.com2026-05-10 → 2026-07-04 · 3 obs

○ 2016-09-23 12:27:20
● 2026-05-10 05:49:02
● 2026-07-04 08:58:26

○NSns2.namebrightdns.com2016-09-23 → 2016-09-23 · 4 obs

○ 2016-03-14 08:18:08
● 2016-09-23 12:27:20
○ 2026-05-10 05:49:02
○ 2026-07-04 08:58:26

○NSns2.uniregistrymarket.link2016-09-23 → 2016-09-23 · 4 obs

○ 2016-03-14 08:18:08
● 2016-09-23 12:27:20
○ 2026-05-10 05:49:02
○ 2026-07-04 08:58:26

○NSsell.internettraffic.com2015-08-06 → 2016-03-14 · 4 obs

● 2015-08-06 22:30:58
● 2016-03-14 08:18:08
○ 2016-09-23 12:27:20
○ 2026-07-04 08:58:26

○MXp.nsm.ctmail.com2016-03-14 → 2016-03-14 · 3 obs

● 2016-03-14 08:18:08
○ 2016-09-23 12:27:20
○ 2026-07-04 08:58:26

○A107.23.198.2402016-09-23 → 2016-09-23 · 4 obs

○ 2016-03-14 08:18:08
● 2016-09-23 12:27:20
○ 2026-05-10 05:49:02
○ 2026-07-04 08:58:26

○A52.206.43.2342016-09-23 → 2016-09-23 · 4 obs

○ 2016-03-14 08:18:08
● 2016-09-23 12:27:20
○ 2026-05-10 05:49:02
○ 2026-07-04 08:58:26

○A52.4.72.1372016-09-23 → 2016-09-23 · 4 obs

○ 2016-03-14 08:18:08
● 2016-09-23 12:27:20
○ 2026-05-10 05:49:02
○ 2026-07-04 08:58:26

○A54.210.33.1902016-09-23 → 2016-09-23 · 4 obs

○ 2016-03-14 08:18:08
● 2016-09-23 12:27:20
○ 2026-05-10 05:49:02
○ 2026-07-04 08:58:26

○A54.236.123.2242016-09-23 → 2016-09-23 · 4 obs

○ 2016-03-14 08:18:08
● 2016-09-23 12:27:20
○ 2026-05-10 05:49:02
○ 2026-07-04 08:58:26

○A69.172.201.2082015-08-06 → 2015-12-06 · 4 obs

● 2015-08-06 22:30:58
● 2015-12-06 15:56:34
○ 2016-03-14 08:18:08
○ 2026-07-04 08:58:26

○A98.124.243.322016-03-14 → 2016-03-14 · 4 obs

○ 2015-12-06 15:56:34
● 2016-03-14 08:18:08
○ 2016-09-23 12:27:20
○ 2026-07-04 08:58:26

○CNAMEhdredirect-lb-399551664.us-east-1.elb.amazonaws.com2016-09-23 → 2016-09-23 · 3 obs

● 2016-09-23 12:27:20
○ 2026-05-10 05:49:02
○ 2026-07-04 08:58:26

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	i.gtld-servers.net, g.gtld-servers.net, m.gtld-servers.net, c.gtld-servers.net...	-
mitcafe.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 mitcafe.com (unsigned zone)

⏱️ Timing

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

Two name servers handle the delegation for nullmx.mitcafe.com: ns1.dns-redirect.com and ns2.dns-redirect.com.

The name server configuration of nullmx.mitcafe.com is shared with other domains, for instance deso.vacations, akillisehirlerkonferansi.com, mlo.kim and two others.

Host names carrying three IP numbers:

The hostname ns1.dns-redirect.com points to 5.161.47.86, 5.161.230.87 and 195.201.128.179.

Host names pointing to two IP addresses:

ns2.dns-redirect.com resolves to two addresses: 76.223.91.20 and 166.117.68.124.