theconnecting.com - dns.ninja

`theconnecting.com`

DNSSEC	⚠️ Not signed
A	13.248.169.48^{🇺🇸 Amazon13.248.160.0/20}
		PTR	`a904c694c05102f30.awsglobalaccelerator.com`
A	76.223.54.146^{🇺🇸 Amazon76.223.48.0/20}
NS	`ns2.afternic.com` ⭐
		A	2603:5:2226::45^{🇺🇸 GODADDY-DNS2603:5:2220::/44}
			PTR	`ns2.afternic.com`
		A	173.201.66.69^{🇺🇸 GODADDY-DNS173.201.66.0/23}
			PTR	`ns2.afternic.com`
NS	`ns1.afternic.com`
		A	2603:5:2126::45^{🇺🇸 GODADDY-DNS2603:5:2120::/44}
			PTR	`ns1.afternic.com`
		A	97.74.98.69^{🇺🇸 GODADDY-DNS97.74.98.0/23}
			PTR	`ns1.afternic.com`
NS	`verification-a3pihk92cq8kttu6igu5bi.ns101.verify.hn` ⚠️ Not in zone NS records
		A	13.248.169.48^{🇺🇸 Amazon13.248.160.0/20}
			PTR	`a904c694c05102f30.awsglobalaccelerator.com`
		A	76.223.54.146^{🇺🇸 Amazon76.223.48.0/20}
			PTR	`a904c694c05102f30.awsglobalaccelerator.com`
TXT	`v=spf1 -all`
SOA	`ns2.afternic.com`dns@jomax.net serial=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=1780597304

Same first word

theconnecting.com

DNS History

19 records (5 active, 14 former)

○NSns09.domaincontrol.com2017-09-25 → 2017-09-25 · 4 obs

○ 2016-11-27 17:00:08
● 2017-09-25 11:28:18
○ 2026-03-20 14:38:40
○ 2026-06-04 18:27:00

●NSns1.afternic.com2026-03-20 → 2026-06-04 · 3 obs

○ 2017-09-25 11:28:18
● 2026-03-20 14:38:40
● 2026-06-04 18:27:00

○NSns1.dynadot.com2015-08-14 → 2016-01-16 · 4 obs

● 2015-08-14 22:55:22
● 2016-01-16 08:59:18
○ 2016-04-26 17:45:20
○ 2026-06-04 18:27:00

○NSns10.domaincontrol.com2017-09-25 → 2017-09-25 · 4 obs

○ 2016-11-27 17:00:08
● 2017-09-25 11:28:18
○ 2026-03-20 14:38:40
○ 2026-06-04 18:27:00

●NSns2.afternic.com2026-03-20 → 2026-06-04 · 3 obs

○ 2017-09-25 11:28:18
● 2026-03-20 14:38:40
● 2026-06-04 18:27:00

○NSns2.dynadot.com2015-08-14 → 2016-01-16 · 4 obs

● 2015-08-14 22:55:22
● 2016-01-16 08:59:18
○ 2016-04-26 17:45:20
○ 2026-06-04 18:27:00

○NSns25.domaincontrol.com2015-08-14 → 2016-11-27 · 4 obs

● 2015-08-14 22:55:22
● 2016-11-27 17:00:08
○ 2017-09-25 11:28:18
○ 2026-06-04 18:27:00

○NSns26.domaincontrol.com2015-08-14 → 2016-11-27 · 4 obs

● 2015-08-14 22:55:22
● 2016-11-27 17:00:08
○ 2017-09-25 11:28:18
○ 2026-06-04 18:27:00

●NSverification-a3pihk92cq8kttu6igu5bi.ns101.verify.hn2026-03-20 → 2026-06-04 · 3 obs

○ 2017-09-25 11:28:18
● 2026-03-20 14:38:40
● 2026-06-04 18:27:00

○MXe5c5cd79008ddb44a63f11bfd5059d.pamx1.hotmail.com2015-08-14 → 2016-11-27 · 4 obs

● 2015-08-14 22:55:22
● 2016-11-27 17:00:08
○ 2017-09-25 11:28:18
○ 2026-06-04 18:27:00

○MXmx.zoho.com2017-09-25 → 2017-09-25 · 4 obs

○ 2016-11-27 17:00:08
● 2017-09-25 11:28:18
○ 2026-03-20 14:38:40
○ 2026-06-04 18:27:00

○MXmx2.zoho.com2017-09-25 → 2017-09-25 · 4 obs

○ 2016-11-27 17:00:08
● 2017-09-25 11:28:18
○ 2026-03-20 14:38:40
○ 2026-06-04 18:27:00

○MXmx3.zoho.com2017-09-25 → 2017-09-25 · 4 obs

○ 2016-11-27 17:00:08
● 2017-09-25 11:28:18
○ 2026-03-20 14:38:40
○ 2026-06-04 18:27:00

○A128.199.183.102015-08-14 → 2015-08-14 · 3 obs

● 2015-08-14 22:55:22
○ 2016-01-16 08:59:18
○ 2026-06-04 18:27:00

●A13.248.169.482026-03-20 → 2026-06-04 · 3 obs

○ 2017-09-25 11:28:18
● 2026-03-20 14:38:40
● 2026-06-04 18:27:00

○A139.59.247.92017-09-25 → 2017-09-25 · 4 obs

○ 2016-11-27 17:00:08
● 2017-09-25 11:28:18
○ 2026-03-20 14:38:40
○ 2026-06-04 18:27:00

○A188.166.229.2052016-11-27 → 2016-11-27 · 4 obs

○ 2016-04-26 17:45:20
● 2016-11-27 17:00:08
○ 2017-09-25 11:28:18
○ 2026-06-04 18:27:00

●A76.223.54.1462026-03-20 → 2026-06-04 · 3 obs

○ 2017-09-25 11:28:18
● 2026-03-20 14:38:40
● 2026-06-04 18:27:00

○A97.74.42.792016-01-16 → 2016-04-26 · 5 obs

○ 2015-08-14 22:55:22
● 2016-01-16 08:59:18
● 2016-04-26 17:45:20
○ 2016-11-27 17:00:08
○ 2026-06-04 18:27:00

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net...	-
theconnecting.com	ns1.afternic.com, ns2.afternic.com, verification-a3pihk92cq8kttu6igu5bi.ns101.verify.hn	4 records

✅ Authoritative Response

Server:97.74.98.69

NS records: ns1.afternic.com, ns2.afternic.com, verification-a3pihk92cq8kttu6igu5bi.ns101.verify.hn

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for theconnecting.com (unsigned zone)

⏱️ Timing

Total: 3952ms | Queries: -

📄 Records

Type	Count	Sample Data
A	2	`76.223.54.146, 13.248.169.48`
NS	2	`ns1.afternic.com, ns2.afternic.com`
MX	1	`. (pri: 0)`
TXT	1	`v=spf1 -all`
SOA	1	`ns1.afternic.com dns.jomax.net`

📌 Glue Records Collected

Total: 4

Out-of-bailiwick: 4 (ns1.afternic.com, ns1.afternic.com, ns2.afternic.com...)

Analysis

IP Addresses

theconnecting.com points to two IP numbers: 13.248.169.48 and 76.223.54.146.

Among the host names that share IP numbers with theconnecting.com are grit.digital, estadioobras.com, story(0x706f726e).com and two others.

Name Servers

DNS for theconnecting.com is handled by three authoritative name servers: ns1.afternic.com, ns2.afternic.com and verification-a3pihk92cq8kttu6igu5bi.ns101.verify.hn.

At least some of theconnecting.com's name servers are shared with other domains, for example mail.hexaclub.com, idhis.com, collectivelasvegas.com and two more.

It is common for these name servers to be used in conjunction with the name servers verification-vesbet7nkettdw2mc9cgox.ns101.verify.hn, verification-jh56ag3qoy8fsktzvbvfht.ns101.verify.hn and verification-cwfnym7gwi8m2hqqfsqc6s.ns101.verify.hn.

Three hostnames — ns1.afternic.com, ns2.afternic.com and verification-a3pihk92cq8kttu6igu5bi.ns101.verify.hn — each have two IP addresses: ns1.afternic.com has 97.74.98.69 and 2603:5:2126::45, ns2.afternic.com has 173.201.66.69 and 2603:5:2226::45, and verification-a3pihk92cq8kttu6igu5bi.ns101.verify.hn has 13.248.169.48 and 76.223.54.146.