diningcorner.com - dns.ninja

`diningcorner.com`

DNSSEC	⚠️ Not signed
A	2606:4700:3030::ac43:95ef^{🇺🇸 Cloudflare2606:4700:3030::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
A	2606:4700:3034::6815:39ce^{🇺🇸 Cloudflare2606:4700:3034::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
A	104.21.57.206^{Cloudflare104.21.48.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
A	172.67.149.239^{🇺🇸 Cloudflare172.67.144.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
NS	`ns1.domainmanage.com` ⭐
		A	2400:cb00:2049:1::adf5:3b04^{🇺🇸 Cloudflare2400:cb00:2049::/48 , Inc. 101 Townsend Street}
		A	173.245.59.4^{🇺🇸 Cloudflare173.245.59.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
NS	`ns2.domainmanage.com`
		A	2400:cb00:2049:1::c629:df27^{🇺🇸 Cloudflare2400:cb00:2049::/48 , Inc. 101 Townsend Street}
		A	198.41.223.39^{Cloudflare198.41.223.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`cf-198-41-223-39.cloudflare.com`
HTTPS	HTTP/3, HTTP/2 ✓ hints match
		IPv4 hints	104.21.57.206, 172.67.149.239
		IPv6 hints	2606:4700:3030::ac43:95ef, 2606:4700:3034::6815:39ce
		ECH	X25519, HKDF-SHA256 + AES-128-GCM draft, id=230, name=cloudflare-ech.com
SOA	`ns1.domainmanage.com`dns@cloudflare.com serial=2408077993

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

Same first word

diningcorner.com

DNS History

17 records (6 active, 11 former)

○NSbuy.internettraffic.com2015-07-24 → 2016-04-17 · 4 obs

● 2015-07-24 10:55:04
● 2016-04-17 03:02:00
○ 2016-11-25 14:37:24
○ 2026-08-11 10:44:28

○NSns1.afternic.com2026-02-15 → 2026-03-27 · 4 obs

○ 2018-01-08 04:01:30
● 2026-02-15 13:24:06
● 2026-03-27 04:09:56
○ 2026-08-11 10:44:28

●NSns1.domainmanage.com2026-08-11 → 2026-08-11 · 2 obs

○ 2026-03-27 04:09:56
● 2026-08-11 10:44:28

○NSns1.uniregistrymarket.link2016-11-25 → 2018-01-08 · 5 obs

○ 2016-04-17 03:02:00
● 2016-11-25 14:37:24
● 2018-01-08 04:01:30
○ 2026-02-15 13:24:06
○ 2026-08-11 10:44:28

○NSns2.afternic.com2026-02-15 → 2026-03-27 · 4 obs

○ 2018-01-08 04:01:30
● 2026-02-15 13:24:06
● 2026-03-27 04:09:56
○ 2026-08-11 10:44:28

●NSns2.domainmanage.com2026-08-11 → 2026-08-11 · 2 obs

○ 2026-03-27 04:09:56
● 2026-08-11 10:44:28

○NSns2.uniregistrymarket.link2016-11-25 → 2018-01-08 · 5 obs

○ 2016-04-17 03:02:00
● 2016-11-25 14:37:24
● 2018-01-08 04:01:30
○ 2026-02-15 13:24:06
○ 2026-08-11 10:44:28

○NSsell.internettraffic.com2015-07-24 → 2016-04-17 · 4 obs

● 2015-07-24 10:55:04
● 2016-04-17 03:02:00
○ 2016-11-25 14:37:24
○ 2026-08-11 10:44:28

○MX.2026-02-15 → 2026-02-16 · 4 obs

● 2026-02-15 13:24:06
● 2026-02-16 02:33:56
○ 2026-03-27 04:09:56
○ 2026-08-11 10:44:28

●A104.21.57.2062026-08-11 → 2026-08-11 · 2 obs

○ 2026-03-27 04:09:56
● 2026-08-11 10:44:28

○A13.248.169.482026-02-15 → 2026-03-27 · 4 obs

○ 2018-01-08 04:01:30
● 2026-02-15 13:24:06
● 2026-03-27 04:09:56
○ 2026-08-11 10:44:28

●A172.67.149.2392026-08-11 → 2026-08-11 · 2 obs

○ 2026-03-27 04:09:56
● 2026-08-11 10:44:28

●A2606:4700:3030::ac43:95ef2026-08-11 → 2026-08-11 · 2 obs

○ 2026-03-27 04:09:56
● 2026-08-11 10:44:28

●A2606:4700:3034::6815:39ce2026-08-11 → 2026-08-11 · 2 obs

○ 2026-03-27 04:09:56
● 2026-08-11 10:44:28

○A69.172.201.1532016-04-17 → 2018-01-08 · 5 obs

○ 2016-01-23 11:35:44
● 2016-04-17 03:02:00
● 2018-01-08 04:01:30
○ 2026-02-15 13:24:06
○ 2026-08-11 10:44:28

○A69.172.201.2082015-07-24 → 2016-01-23 · 4 obs

● 2015-07-24 10:55:04
● 2016-01-23 11:35:44
○ 2016-04-17 03:02:00
○ 2026-08-11 10:44:28

○A76.223.54.1462026-02-15 → 2026-03-27 · 4 obs

○ 2018-01-08 04:01:30
● 2026-02-15 13:24:06
● 2026-03-27 04:09:56
○ 2026-08-11 10:44:28

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net...	-
diningcorner.com	ns1.domainmanage.com, ns2.domainmanage.com	2 records

✅ Authoritative Response

Server:173.245.59.4

NS records: ns1.domainmanage.com, ns2.domainmanage.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for diningcorner.com (unsigned zone)

⏱️ Timing

Total: 76ms | Queries: -

📄 Records

Type	Count	Sample Data
A	2	`172.67.149.239, 104.21.57.206`
AAAA	2	`2606:4700:3030::ac43:95ef, 2606:4700:3034::6815:39ce`
NS	2	`ns1.domainmanage.com, ns2.domainmanage.com`
HTTPS	1	`{"priority":1,"target":".","alpn":["h3",`
SOA	1	`ns1.domainmanage.com dns.cloudflare.com`

📌 Glue Records Collected

Total: 2

Out-of-bailiwick: 2 (ns1.domainmanage.com, ns2.domainmanage.com)

Analysis

IP Addresses

diningcorner.com directs to four IP numbers, which are 104.21.57.206, 172.67.149.239, 2606:4700:3030::ac43:95ef and 2606:4700:3034::6815:39ce.

51pla.com.cn, whxyhotel.com, www.newswire.com.br plus two other host names have IP numbers in common with diningcorner.com.

Name Servers

diningcorner.com uses two name servers for its delegation: ns1.domainmanage.com and ns2.domainmanage.com.

The name server configuration of diningcorner.com is shared with other domains, for instance artsbarn.com, wildreviews.com, coset.net and two others.

The two host names ns1.domainmanage.com and ns2.domainmanage.com each have a pair of IP addresses: ns1.domainmanage.com has 173.245.59.4 and 2400:cb00:2049:1::adf5:3b04, and ns2.domainmanage.com has 198.41.223.39 and 2400:cb00:2049:1::c629:df27.