`futilequest.com`

DNSSEC	⚠️ Not signed
A	2600:9000:a612:55d9:1b82:e963:5969:d2c7^{🇺🇸 Amazon2600:9000:a600::/43}
		PTR	`ad988eeb126877ff9.dualstack.awsglobalaccelerator.com`
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: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	76.223.91.20^{🇺🇸 Amazon76.223.80.0/20}
A	195.201.128.179^{🇩🇪 Hetzner195.201.0.0/16 HETZNER-DC}
NS	`ns1.dns-redirect.com` ⭐
		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`
		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`
TXT	`95b3a950-315c-45b8-937a-b865ebeb043a`
TXT	`afternic-verification-aGHTsEA2nLa7KRqzmJySAx`
SOA	`ns1.dns-redirect.com`admin@redirhub.com 2024-07-29 #1

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

Same first word

futilequest.com

DNS History

27 records (12 active, 15 former)

●NSns1.dns-redirect.com2026-03-12 → 2026-05-10 · 3 obs

○ 2018-01-05 21:04:30
● 2026-03-12 21:40:36
● 2026-05-10 09:06:58

○NSns1.namebrightdns.com2016-01-02 → 2018-01-05 · 5 obs

○ 2015-11-01 13:27:28
● 2016-01-02 21:30:08
● 2018-01-05 21:04:30
○ 2026-03-12 21:40:36
○ 2026-05-10 09:06:58

●NSns2.dns-redirect.com2026-03-12 → 2026-05-10 · 3 obs

○ 2018-01-05 21:04:30
● 2026-03-12 21:40:36
● 2026-05-10 09:06:58

○NSns2.namebrightdns.com2016-01-02 → 2018-01-05 · 5 obs

○ 2015-11-01 13:27:28
● 2016-01-02 21:30:08
● 2018-01-05 21:04:30
○ 2026-03-12 21:40:36
○ 2026-05-10 09:06:58

○NSnsg1.namebrightdns.com2015-06-12 → 2015-11-01 · 4 obs

● 2015-06-12 22:32:26
● 2015-11-01 13:27:28
○ 2016-01-02 21:30:08
○ 2026-05-10 09:06:58

○NSnsg2.namebrightdns.com2015-06-12 → 2015-11-01 · 4 obs

● 2015-06-12 22:32:26
● 2015-11-01 13:27:28
○ 2016-01-02 21:30:08
○ 2026-05-10 09:06:58

○MXanmail.namebrightmail.com2015-06-12 → 2015-06-12 · 3 obs

● 2015-06-12 22:32:26
○ 2015-11-01 13:27:28
○ 2026-05-10 09:06:58

○A107.21.42.1422016-04-03 → 2016-04-03 · 4 obs

○ 2016-01-02 21:30:08
● 2016-04-03 14:56:30
○ 2017-01-01 03:16:48
○ 2026-05-10 09:06:58

○A107.23.160.2182016-01-02 → 2016-01-02 · 4 obs

○ 2015-11-01 13:27:28
● 2016-01-02 21:30:08
○ 2016-04-03 14:56:30
○ 2026-05-10 09:06:58

●A195.201.128.1792026-03-12 → 2026-05-10 · 3 obs

○ 2018-01-05 21:04:30
● 2026-03-12 21:40:36
● 2026-05-10 09:06:58

●A2600:9000:a612:55d9:1b82:e963:5969:d2c72026-03-12 → 2026-05-10 · 3 obs

○ 2018-01-05 21:04:30
● 2026-03-12 21:40:36
● 2026-05-10 09:06:58

●A2a01:4f8:1c1e:d6f1::12026-03-12 → 2026-05-10 · 3 obs

○ 2018-01-05 21:04:30
● 2026-03-12 21:40:36
● 2026-05-10 09:06:58

●A2a01:4ff:1f0:dd50::12026-03-12 → 2026-05-10 · 3 obs

○ 2018-01-05 21:04:30
● 2026-03-12 21:40:36
● 2026-05-10 09:06:58

●A2a01:4ff:f0:5f41::12026-03-12 → 2026-05-10 · 3 obs

○ 2018-01-05 21:04:30
● 2026-03-12 21:40:36
● 2026-05-10 09:06:58

●A46.62.237.1382026-03-12 → 2026-05-10 · 3 obs

○ 2018-01-05 21:04:30
● 2026-03-12 21:40:36
● 2026-05-10 09:06:58

●A5.161.230.872026-03-12 → 2026-05-10 · 3 obs

○ 2018-01-05 21:04:30
● 2026-03-12 21:40:36
● 2026-05-10 09:06:58

●A5.161.47.862026-03-12 → 2026-05-10 · 3 obs

○ 2018-01-05 21:04:30
● 2026-03-12 21:40:36
● 2026-05-10 09:06:58

●A5.78.156.592026-03-12 → 2026-05-10 · 3 obs

○ 2018-01-05 21:04:30
● 2026-03-12 21:40:36
● 2026-05-10 09:06:58

○A54.174.149.302016-04-03 → 2016-04-03 · 4 obs

○ 2016-01-02 21:30:08
● 2016-04-03 14:56:30
○ 2017-01-01 03:16:48
○ 2026-05-10 09:06:58

○A54.174.31.2542015-06-12 → 2015-11-01 · 4 obs

● 2015-06-12 22:32:26
● 2015-11-01 13:27:28
○ 2016-01-02 21:30:08
○ 2026-05-10 09:06:58

○A54.208.74.2152015-06-12 → 2015-11-01 · 4 obs

● 2015-06-12 22:32:26
● 2015-11-01 13:27:28
○ 2016-01-02 21:30:08
○ 2026-05-10 09:06:58

○A54.209.90.812016-01-02 → 2016-01-02 · 4 obs

○ 2015-11-01 13:27:28
● 2016-01-02 21:30:08
○ 2016-04-03 14:56:30
○ 2026-05-10 09:06:58

○A54.82.156.192017-01-01 → 2017-01-01 · 4 obs

○ 2016-04-03 14:56:30
● 2017-01-01 03:16:48
○ 2018-01-05 21:04:30
○ 2026-05-10 09:06:58

○A54.86.225.1562017-01-01 → 2017-01-01 · 4 obs

○ 2016-04-03 14:56:30
● 2017-01-01 03:16:48
○ 2018-01-05 21:04:30
○ 2026-05-10 09:06:58

●A76.223.91.202026-03-12 → 2026-05-10 · 3 obs

○ 2018-01-05 21:04:30
● 2026-03-12 21:40:36
● 2026-05-10 09:06:58

○CNAMEhdredirect-lb-399551664.us-east-1.elb.amazonaws.com2015-06-12 → 2016-04-03 · 4 obs

● 2015-06-12 22:32:26
● 2016-04-03 14:56:30
○ 2017-01-01 03:16:48
○ 2026-05-10 09:06:58

○CNAMEhdredirect-lb3-890977680.us-east-1.elb.amazonaws.com2017-01-01 → 2018-01-05 · 5 obs

○ 2016-04-03 14:56:30
● 2017-01-01 03:16:48
● 2018-01-05 21:04:30
○ 2026-03-12 21:40:36
○ 2026-05-10 09:06: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...	-
futilequest.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 futilequest.com (unsigned zone)

⏱️ Timing

Total: 213ms | Queries: -

📄 Records

Type	Count	Sample Data
A	6	`5.161.230.87, 46.62.237.138...`
AAAA	4	`2a01:4ff:1f0:dd50::1, 2a01:4f8:1c1e:d6f1::1...`
NS	2	`ns1.dns-redirect.com, ns2.dns-redirect.com`
TXT	2	`95b3a950-315c-45b8-937a-b865ebeb043a, afternic-verification-aGHTsEA2nLa7KRqzmJ`
SOA	1	`ns1.dns-redirect.com admin.redirhub.com`

📌 Glue Records Collected

Total: 5

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

Analysis

IP Addresses

Ten IP numbers are pointed to by futilequest.com: 2600:9000:a612:55d9:1b82:e963:5969:d2c7, 2a01:4f8:1c1e:d6f1::1, 2a01:4ff:f0:5f41::1, 2a01:4ff:1f0:dd50::1, 5.78.156.59, 5.161.47.86, 5.161.230.87, 46.62.237.138, 76.223.91.20 and 195.201.128.179.

Other host names, for instance www.coppercranberrylamp.com, escsupport.com, emmanoah-losangeles.com, metaem.com and fortbendimpact.com share IP numbers with futilequest.com.

Name Servers

Two name servers ns1.dns-redirect.com and ns2.dns-redirect.com are delegated to futilequest.com.

futilequest.com uses the same name server configuration as other domains, such as meinw.com, aktistech.com, uicllc.com, kode.academy and valleysilicons.online.

Three IP numbers: ns1.dns-redirect.com correspond to 5.161.47.86, 5.161.230.87 and 195.201.128.179.

Two IP numbers: ns2.dns-redirect.com correspond to 76.223.91.20 and 166.117.68.124.

futilequest.com - robtex.com

futilequest.com

com

Same first word

DNS History

🔍 DNS Trace

📋 Delegation Chain

✅ Authoritative Response

🔒 DNSSEC Status

⏱️ Timing

📄 Records

📌 Glue Records Collected

Analysis

IP Addresses

Name Servers

`futilequest.com`

`com`