ns1.babylonconnect.com - robtex.com

ns1.babylonconnect.com

DNSSEC⚠️ Not signed
A173.248.129.180🇺🇸 WEHOST173.248.128.0/18 NET-WEHOST-3

babylonconnect.com

DNSSEC⚠️ Not signed
A216.40.34.41🇨🇦 TUCOWS216.40.34.0/24
NSns1.hover.com
NSns2.hover.com
NSns3.hover.com ⚠️ Not in zone NS records
SOAns1.hover.comdnsmaster@hover.com serial=1784378981

Previously NS for

Same first word

Similar names

DNS History

1 record (1 active, 0 former)

20162017201820192020202120222023202420252026A173.248.129.180
A173.248.129.1802015-07-01 → 2026-07-19 · 2 obs
● 2015-07-01 23:53:04
● 2026-07-19 15:02:10

🔍 DNS Trace

📋 Delegation Chain

ZoneNameserversGlue
coma.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net...-
babylonconnect.comns3.hover.com, ns1.hover.com, ns2.hover.com6 records

✅ Authoritative Response

Server:64.98.148.13

NS records: ns3.hover.com, ns1.hover.com, ns2.hover.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for babylonconnect.com (unsigned zone)

⏱️ Timing

Total: 128ms | Queries: -

📄 Records

TypeCountSample Data
A1173.248.129.180

📌 Glue Records Collected

Total: 6

Out-of-bailiwick: 6 (ns3.hover.com, ns3.hover.com, ns1.hover.com...)

Analysis

IP Addresses

ns1.babylonconnect.com has exactly one IP address — 173.248.129.180.

Among the host names that share IP numbers with ns1.babylonconnect.com is ns2.babylonconnect.com, as one example.