`diningsb.com`

DNSSEC	⚠️ Not signed
A	44.236.157.164^{🇺🇸 Amazon44.224.0.0/11 EC2 PDX prefix}
		PTR	`ec2-44-236-157-164.us-west-2.compute.amazonaws.com`
NS	`dns1.name-services.com` ⭐
		A	2604:4000:2800:2000:64:98:148:137^{🇨🇦 TUCOWS-32604:4000:2800::/37 Tucows.com Co.}
			PTR	`dns1.name-services.com`
		A	64.98.148.137^{🇨🇦 TUCOWS-364.98.144.0/20 Tucows.com Co.}
			PTR	`dns1.name-services.com`
NS	`dns2.name-services.com`
		A	2604:4000:0:d:216:40:47:201^{🇨🇦 TUCOWS2604:4000::/48 -BRA-IPV6-BLK1.1/NET-2604:4000}
			PTR	`dns2.name-services.com`
		A	216.40.47.201^{🇨🇦 TUCOWS216.40.47.0/24 -BRA-BLK1.4/NET-216-40-47-0}
			PTR	`dns2.name-services.com`
NS	`dns3.name-services.com`
		A	2604:4000:2800:2000:64:98:148:138^{🇨🇦 TUCOWS-32604:4000:2800::/37 Tucows.com Co.}
			PTR	`dns3.name-services.com`
		A	64.98.148.138^{🇨🇦 TUCOWS-364.98.144.0/20 Tucows.com Co.}
			PTR	`dns3.name-services.com`
NS	`dns4.name-services.com`
		A	2604:4000:0:d:216:40:47:202^{🇨🇦 TUCOWS2604:4000::/48 -BRA-IPV6-BLK1.1/NET-2604:4000}
			PTR	`dns4.name-services.com`
		A	216.40.47.202^{🇨🇦 TUCOWS216.40.47.0/24 -BRA-BLK1.4/NET-216-40-47-0}
			PTR	`dns4.name-services.com`
NS	`dns5.name-services.com`
		A	2604:4000:2800:2000:64:98:148:139^{🇨🇦 TUCOWS-32604:4000:2800::/37 Tucows.com Co.}
			PTR	`dns5.name-services.com`
		A	64.98.148.139^{🇨🇦 TUCOWS-364.98.144.0/20 Tucows.com Co.}
			PTR	`dns5.name-services.com`
SOA	`dns1.name-services.com`info@name-services.com serial=1775675918

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

Same first word

diningsb.com

Similar names

bindings.de

bindings.io

bindings.com.au

bindings.ai

DNS History

13 records (6 active, 7 former)

●NSdns1.name-services.com2007-11-12 → 2026-08-05 · 5 obs

● 2007-11-12 18:58:52
○ 2015-08-03 15:49:36
○ 2026-04-02 23:48:16
● 2026-05-06 20:46:30
● 2026-08-05 03:15:22

●NSdns2.name-services.com2007-11-12 → 2026-08-05 · 5 obs

● 2007-11-12 18:58:52
○ 2015-08-03 15:49:36
○ 2026-04-02 23:48:16
● 2026-05-06 20:46:30
● 2026-08-05 03:15:22

●NSdns3.name-services.com2007-11-12 → 2026-08-05 · 5 obs

● 2007-11-12 18:58:52
○ 2015-08-03 15:49:36
○ 2026-04-02 23:48:16
● 2026-05-06 20:46:30
● 2026-08-05 03:15:22

●NSdns4.name-services.com2007-11-12 → 2026-08-05 · 5 obs

● 2007-11-12 18:58:52
○ 2015-08-03 15:49:36
○ 2026-04-02 23:48:16
● 2026-05-06 20:46:30
● 2026-08-05 03:15:22

●NSdns5.name-services.com2007-11-12 → 2026-08-05 · 5 obs

● 2007-11-12 18:58:52
○ 2015-08-03 15:49:36
○ 2026-04-02 23:48:16
● 2026-05-06 20:46:30
● 2026-08-05 03:15:22

○NSns11.tangohosting.com2026-04-02 → 2026-04-02 · 4 obs

○ 2017-03-20 18:37:50
● 2026-04-02 23:48:16
○ 2026-05-06 20:46:30
○ 2026-08-05 03:15:22

○NSns12.tangohosting.com2026-04-02 → 2026-04-02 · 4 obs

○ 2017-03-20 18:37:50
● 2026-04-02 23:48:16
○ 2026-05-06 20:46:30
○ 2026-08-05 03:15:22

○NSns3.tangohosting.com2015-08-03 → 2017-03-20 · 5 obs

○ 2007-11-12 18:58:52
● 2015-08-03 15:49:36
● 2017-03-20 18:37:50
○ 2026-04-02 23:48:16
○ 2026-08-05 03:15:22

○NSns4.tangohosting.com2015-08-03 → 2017-03-20 · 5 obs

○ 2007-11-12 18:58:52
● 2015-08-03 15:49:36
● 2017-03-20 18:37:50
○ 2026-04-02 23:48:16
○ 2026-08-05 03:15:22

○MXmx01.tangohosting.com2015-08-03 → 2017-03-20 · 5 obs

○ 2007-11-12 18:58:52
● 2015-08-03 15:49:36
● 2017-03-20 18:37:50
○ 2026-04-02 23:48:16
○ 2026-08-05 03:15:22

○A205.134.226.312015-08-03 → 2017-03-20 · 5 obs

○ 2007-11-12 18:58:52
● 2015-08-03 15:49:36
● 2017-03-20 18:37:50
○ 2026-04-02 23:48:16
○ 2026-08-05 03:15:22

○A216.52.184.2432007-11-12 → 2007-11-12 · 3 obs

● 2007-11-12 18:58:52
○ 2015-08-03 15:49:36
○ 2026-08-05 03:15:22

●A44.236.157.1642026-05-06 → 2026-08-05 · 3 obs

○ 2026-04-02 23:48:16
● 2026-05-06 20:46:30
● 2026-08-05 03:15:22

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	m.gtld-servers.net, f.gtld-servers.net, g.gtld-servers.net, d.gtld-servers.net...	-
diningsb.com	dns1.name-services.com, dns2.name-services.com, dns3.name-services.com, dns4.name-services.com...	10 records

✅ Authoritative Response

Server:64.98.148.139

NS records: dns1.name-services.com, dns2.name-services.com, dns3.name-services.com, dns4.name-services.com, dns5.name-services.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for diningsb.com (unsigned zone)

⏱️ Timing

Total: 611ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`44.236.157.164`
NS	5	`dns1.name-services.com, dns2.name-services.com...`
SOA	1	`dns1.name-services.com info.name-service`

📌 Glue Records Collected

Total: 10

Out-of-bailiwick: 10 (dns1.name-services.com, dns1.name-services.com, dns2.name-services.com...)

Analysis

IP Addresses

diningsb.com has exactly one IP address — 44.236.157.164.

loschoppers.com, tbpm.org, intelametrix.com plus two other host names have IP numbers in common with diningsb.com.

Name Servers

Five name servers handle delegation for diningsb.com: dns1.name-services.com, dns2.name-services.com, dns3.name-services.com and two others.

diningsb.com shares at least some of its name servers with other domains, including tuckers.co.uk, ictsynergy.com, cashpatios.com and two others.

These name servers are frequently paired with the name servers dns4.name-services.com and dns5.name-services.com.

Host names pointing to two IP addresses:

dns1.name-services.com resolves to 64.98.148.137 and 2604:4000:2800:2000:64:98:148:137.

dns2.name-services.com resolves to 216.40.47.201 and 2604:4000:0:d:216:40:47:201.

dns3.name-services.com resolves to 64.98.148.138 and 2604:4000:2800:2000:64:98:148:138.

dns4.name-services.com resolves to 216.40.47.202 and 2604:4000:0:d:216:40:47:202.

dns5.name-services.com resolves to 64.98.148.139 and 2604:4000:2800:2000:64:98:148:139.