nextrequest.net - dns.ninja

`nextrequest.net`

DNSSEC	⚠️ Not signed
A	184.168.29.3^{🇺🇸 AS398101184.168.28.0/22}
		PTR	`3.29.168.184.host.secureserver.net`
NS	`ns33.domaincontrol.com` ⭐
		A	2603:5:21a1::11^{🇺🇸 GODADDY-DNS2603:5:21a0::/44}
			PTR	`ns33.domaincontrol.com`
		A	97.74.106.17^{🇺🇸 GODADDY-DNS97.74.106.0/23}
			PTR	`ns33.domaincontrol.com`
NS	`ns34.domaincontrol.com`
		A	2603:5:22a1::11^{🇺🇸 GODADDY-DNS2603:5:22a0::/44}
			PTR	`ns34.domaincontrol.com`
		A	173.201.74.17^{🇺🇸 GODADDY-DNS173.201.74.0/23}
			PTR	`ns34.domaincontrol.com`
MX	`nextrequest-net.mail.protection.outlook.com` ⭐
		A	2a01:111:f403:c902::^{🇺🇸 Microsoft2a01:111:f000::/36}
			PTR	`mail-sj2pr05cu00300.inbound.protection.outlook.com`
		A	2a01:111:f403:c922::2^{🇺🇸 Microsoft2a01:111:f000::/36}
			PTR	`mail-bl0pr02cu00702.inbound.protection.outlook.com`
		A	2a01:111:f403:c92c::3^{🇺🇸 Microsoft2a01:111:f000::/36}
			PTR	`mail-dm5pr04cu00103.inbound.protection.outlook.com`
		A	2a01:111:f403:f901::1^{🇺🇸 Microsoft2a01:111:f000::/36}
			PTR	`mail-bl0pr02cu00601.inbound.protection.outlook.com`
		A	52.101.8.46^{🇺🇸 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-dm6pr05cu00406.inbound.protection.outlook.com`
		A	52.101.9.24^{🇺🇸 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-bl2pr02cu00400.inbound.protection.outlook.com`
		A	52.101.11.19^{🇺🇸 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-sa9pr04cu00203.inbound.protection.outlook.com`
		A	52.101.42.18^{🇺🇸 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-co1pr03cu00302.inbound.protection.outlook.com`
TXT	`google-site-verification=3PGGXnDhqZc65b87ZmS_APeTL7T7Tx519FNwDkyoo-s`
TXT	`NETORGFT15253214.onmicrosoft.com`
TXT	`v=spf1 include:secureserver.net -all`
SOA	`ns33.domaincontrol.com`dns@jomax.net 2025-09-24 #0

`net`

	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=1786688454

Same first word

nextrequest.net

nextrequest.com

DNS History

11 records (4 active, 7 former)

●NSns33.domaincontrol.com2026-04-08 → 2026-08-14 · 3 obs

○ 2018-10-16 20:57:32
● 2026-04-08 02:33:54
● 2026-08-14 06:51:04

●NSns34.domaincontrol.com2026-04-08 → 2026-08-14 · 3 obs

○ 2018-10-16 20:57:32
● 2026-04-08 02:33:54
● 2026-08-14 06:51:04

○NSns73.domaincontrol.com2015-06-28 → 2018-10-16 · 4 obs

● 2015-06-28 14:27:48
● 2018-10-16 20:57:32
○ 2026-04-08 02:33:54
○ 2026-08-14 06:51:04

○NSns74.domaincontrol.com2015-06-28 → 2018-10-16 · 4 obs

● 2015-06-28 14:27:48
● 2018-10-16 20:57:32
○ 2026-04-08 02:33:54
○ 2026-08-14 06:51:04

○MXmailstore1.secureserver.net2015-06-28 → 2018-10-16 · 4 obs

● 2015-06-28 14:27:48
● 2018-10-16 20:57:32
○ 2026-04-08 02:33:54
○ 2026-08-14 06:51:04

●MXnextrequest-net.mail.protection.outlook.com2026-04-08 → 2026-08-14 · 3 obs

○ 2018-10-16 20:57:32
● 2026-04-08 02:33:54
● 2026-08-14 06:51:04

○MXsmtp.secureserver.net2015-06-28 → 2018-10-16 · 4 obs

● 2015-06-28 14:27:48
● 2018-10-16 20:57:32
○ 2026-04-08 02:33:54
○ 2026-08-14 06:51:04

○A166.62.93.2112016-04-22 → 2018-10-16 · 5 obs

○ 2016-01-27 12:43:16
● 2016-04-22 07:43:18
● 2018-10-16 20:57:32
○ 2026-04-08 02:33:54
○ 2026-08-14 06:51:04

●A184.168.29.32026-04-08 → 2026-08-14 · 3 obs

○ 2018-10-16 20:57:32
● 2026-04-08 02:33:54
● 2026-08-14 06:51:04

○A65.182.187.1252015-06-28 → 2015-06-28 · 3 obs

● 2015-06-28 14:27:48
○ 2015-11-03 07:50:20
○ 2026-08-14 06:51:04

○A68.178.200.2262015-11-03 → 2016-01-27 · 5 obs

○ 2015-06-28 14:27:48
● 2015-11-03 07:50:20
● 2016-01-27 12:43:16
○ 2016-04-22 07:43:18
○ 2026-08-14 06:51:04

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
net	m.gtld-servers.net, g.gtld-servers.net, i.gtld-servers.net, b.gtld-servers.net...	-
nextrequest.net	ns33.domaincontrol.com, ns34.domaincontrol.com	-

✅ Authoritative Response

Server:97.74.106.17

NS records: ns33.domaincontrol.com, ns34.domaincontrol.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for nextrequest.net (unsigned zone)

⏱️ Timing

Total: 246ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`184.168.29.3`
NS	2	`ns33.domaincontrol.com, ns34.domaincontrol.com`
MX	1	`nextrequest-net.mail.protection.outlook.`
TXT	3	`google-site-verification=3PGGXnDhqZc65b8, NETORGFT15253214.onmicrosoft.com...`
SOA	1	`ns33.domaincontrol.com dns.jomax.net`

Analysis

IP Addresses

nextrequest.net resolves to one IP address: 184.168.29.3.

liquidgooey.com, 3.29.168.184.host.secureserver.net, shanesummers.com and two other host names share IP numbers with nextrequest.net.

Name Servers

nextrequest.net uses two name servers for its delegation: ns33.domaincontrol.com and ns34.domaincontrol.com.

nextrequest.net uses the same name servers as several other domains — among them millercreekfinancial.com, e-bug.net, cbrw.com and two more.

nextrequest.net has a partial name server overlap with other domains — among them farmersco-op.com and abtach.org.

The two host names ns33.domaincontrol.com and ns34.domaincontrol.com each have a pair of IP addresses: ns33.domaincontrol.com has 97.74.106.17 and 2603:5:21a1::11, and ns34.domaincontrol.com has 173.201.74.17 and 2603:5:22a1::11.

Mail Servers

Mail for nextrequest.net is handled by a single mail server, nextrequest-net.mail.protection.outlook.com.

nextrequest-net.mail.protection.outlook.com resolves to 8 IP addresses — 52.101.8.46, 52.101.9.24, 52.101.11.19 and 5 others.