`therestaurantguide.net`

DNSSEC	⚠️ Not signed
A	172.234.24.211^{🇺🇸 AKAMAI-LINODE-AP172.234.16.0/20 Akamai Technologies}
		PTR	`k8s-svc-lander-namecheap-expired-us-ord-02.parklogic.net`
A	172.239.57.117^{🇺🇸 AKAMAI-LINODE-AP172.239.32.0/19 Akamai Technologies}
NS	`dns101.registrar-servers.com` ⭐
		A	2600:3c02::f03c:93ff:febe:d723^{🇺🇸 AKAMAI-LINODE-AP2600:3c02::/32 Akamai Technologies}
		A	170.187.200.230^{🇺🇸 AKAMAI-LINODE-AP170.187.200.0/21 Akamai Technologies}
			PTR	`latte.parklogic.com`
NS	`dns102.registrar-servers.com`
		A	2600:3c02::f03c:93ff:febe:c249^{🇺🇸 AKAMAI-LINODE-AP2600:3c02::/32 Akamai Technologies}
		A	23.239.17.221^{🇺🇸 AKAMAI-LINODE-AP23.239.16.0/22 Akamai Technologies}
			PTR	`merlot.parklogic.com`
MX	`mx.plingest.com` ⭐
		A	38.143.66.193^{🇺🇸 AS6302338.143.66.0/24 Proxy-registered route object 2011686}
			PTR	`193-66-143-38.clients.gthost.com`
TXT	`v=spf1 -all`
SOA	`dns101.registrar-servers.com`hostmaster@parklogic.com 2021-05-19 #1

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

Same first word

therestaurantguide.net

therestaurantguide.com

therestaurantguide.co.nz

DNS History

20 records (5 active, 15 former)

○NSdns1.name-services.com2015-05-22 → 2016-09-15 · 4 obs

● 2015-05-22 21:35:46
● 2016-09-15 16:32:46
○ 2017-12-24 06:32:40
○ 2026-03-26 06:56:10

●NSdns101.registrar-servers.com2026-03-26 → 2026-03-26 · 3 obs

○ 2017-12-24 06:32:40
● 2026-03-26 06:56:08
● 2026-03-26 06:56:10

●NSdns102.registrar-servers.com2026-03-26 → 2026-03-26 · 3 obs

○ 2017-12-24 06:32:40
● 2026-03-26 06:56:08
● 2026-03-26 06:56:10

○NSdns2.name-services.com2015-05-22 → 2016-09-15 · 4 obs

● 2015-05-22 21:35:46
● 2016-09-15 16:32:46
○ 2017-12-24 06:32:40
○ 2026-03-26 06:56:10

○NSdns3.name-services.com2015-05-22 → 2016-09-15 · 4 obs

● 2015-05-22 21:35:46
● 2016-09-15 16:32:46
○ 2017-12-24 06:32:40
○ 2026-03-26 06:56:10

○NSdns4.name-services.com2015-05-22 → 2016-09-15 · 4 obs

● 2015-05-22 21:35:46
● 2016-09-15 16:32:46
○ 2017-12-24 06:32:40
○ 2026-03-26 06:56:10

○NSdns5.name-services.com2015-05-22 → 2016-09-15 · 4 obs

● 2015-05-22 21:35:46
● 2016-09-15 16:32:46
○ 2017-12-24 06:32:40
○ 2026-03-26 06:56:10

○NSns1.dnsip.com2026-03-26 → 2026-03-26 · 2 obs

○ 2026-03-26 06:56:08
○ 2026-03-26 06:56:10

○NSns1.namefind.com2017-12-24 → 2017-12-24 · 4 obs

○ 2016-09-15 16:32:46
● 2017-12-24 06:32:40
○ 2026-03-26 06:56:08
○ 2026-03-26 06:56:10

○NSns2.dnsip.com2026-03-26 → 2026-03-26 · 2 obs

○ 2026-03-26 06:56:08
○ 2026-03-26 06:56:10

○NSns2.namefind.com2017-12-24 → 2017-12-24 · 4 obs

○ 2016-09-15 16:32:46
● 2017-12-24 06:32:40
○ 2026-03-26 06:56:08
○ 2026-03-26 06:56:10

○MXmail.b-io.co2015-05-22 → 2016-09-15 · 4 obs

● 2015-05-22 21:35:46
● 2016-09-15 16:32:46
○ 2017-12-24 06:32:40
○ 2026-03-26 06:56:10

●MXmx.plingest.com2026-03-26 → 2026-03-26 · 3 obs

○ 2017-12-24 06:32:40
● 2026-03-26 06:56:08
● 2026-03-26 06:56:10

○MXp.nsm.ctmail.com2015-05-22 → 2016-03-29 · 4 obs

● 2015-05-22 21:35:46
● 2016-03-29 16:56:32
○ 2016-09-15 16:32:46
○ 2026-03-26 06:56:10

●A172.234.24.2112026-03-26 → 2026-03-26 · 3 obs

○ 2017-12-24 06:32:40
● 2026-03-26 06:56:08
● 2026-03-26 06:56:10

●A172.239.57.1172026-03-26 → 2026-03-26 · 3 obs

○ 2017-12-24 06:32:40
● 2026-03-26 06:56:08
● 2026-03-26 06:56:10

○A34.96.147.2362026-03-26 → 2026-03-26 · 2 obs

○ 2026-03-26 06:56:08
○ 2026-03-26 06:56:10

○A64.74.223.372015-05-22 → 2015-12-29 · 4 obs

● 2015-05-22 21:35:46
● 2015-12-29 17:43:02
○ 2016-03-29 16:56:32
○ 2026-03-26 06:56:10

○A68.178.213.612017-12-24 → 2017-12-24 · 4 obs

○ 2016-09-15 16:32:46
● 2017-12-24 06:32:40
○ 2026-03-26 06:56:08
○ 2026-03-26 06:56:10

○A98.124.243.372016-03-29 → 2016-09-15 · 5 obs

○ 2015-12-29 17:43:02
● 2016-03-29 16:56:32
● 2016-09-15 16:32:46
○ 2017-12-24 06:32:40
○ 2026-03-26 06:56:10

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
net	a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net...	-
therestaurantguide.net	dns101.registrar-servers.com, dns102.registrar-servers.com	-

✅ Authoritative Response

Server:23.239.17.221

NS records: dns101.registrar-servers.com, dns102.registrar-servers.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for therestaurantguide.net (unsigned zone)

⏱️ Timing

Total: 608ms | Queries: -

📄 Records

Type	Count	Sample Data
A	2	`172.239.57.117, 172.234.24.211`
NS	2	`dns102.registrar-servers.com, dns101.registrar-servers.com`
MX	1	`mx.plingest.com (pri: 10)`
TXT	1	`v=spf1 -all`
SOA	1	`dns101.registrar-servers.com hostmaster.`

Analysis

IP Addresses

therestaurantguide.net points to two IPs: 172.234.24.211 and 172.239.57.117.

Other host names, for instance amarantum.com, ns1.teen(0x736578).site, mail4.archivoklf.pro, banyanthemes.com and hotrodienmayxanh.com share IP numbers with therestaurantguide.net.

Name Servers

Two name servers dns101.registrar-servers.com and dns102.registrar-servers.com are delegated to therestaurantguide.net.

therestaurantguide.net uses the same name server configuration as other domains, such as mx.phonia.host, whobrokeamerica.com, thecakemaker.in, adbooth.net and gameschef.com.

Host names with two IPs:

dns101.registrar-servers.com points to 2600:3c02::f03c:93ff:febe:d723 and 170.187.200.230.

dns102.registrar-servers.com points to 2600:3c02::f03c:93ff:febe:c249 and 23.239.17.221.

Mail Servers

therestaurantguide.net is handled by a single mail server, mx.plingest.com.

therestaurantguide.net shares the same mail server setup as other domains, including 7jp.com, ab08e252a5c3.k-c.info, zinntitle.com, bloodyobvious.com and mimonails.com.

mx.plingest.com points to one IP number: 38.143.66.193.

therestaurantguide.net - robtex.com