bridgle.com - robtex.com
bridgle.com
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.netnstld@verisign-grs.com serial=1774629632 | ||||||
Same first word
bridgle.com |
Similar names
DNS History
9 records (4 active, 5 former)
●NSns-cloud-a1.googledomains.com2026-03-09 → 2026-03-27 · 3 obs
● 2026-03-09 02:38:14
● 2026-03-27 16:42:42
●NSns-cloud-a2.googledomains.com2026-03-09 → 2026-03-27 · 3 obs
● 2026-03-09 02:38:14
● 2026-03-27 16:42:42
●NSns-cloud-a3.googledomains.com2026-03-09 → 2026-03-27 · 3 obs
● 2026-03-09 02:38:14
● 2026-03-27 16:42:42
●NSns-cloud-a4.googledomains.com2026-03-09 → 2026-03-27 · 3 obs
● 2026-03-09 02:38:14
● 2026-03-27 16:42:42
○NSns29.domaincontrol.com2017-03-19 → 2017-03-19 · 3 obs
○ 2019-03-23 21:12:32
○ 2026-03-27 16:42:42
○NSns30.domaincontrol.com2017-03-19 → 2017-03-19 · 3 obs
○ 2019-03-23 21:12:32
○ 2026-03-27 16:42:42
○MXmailstore1.secureserver.net2017-03-19 → 2017-03-19 · 3 obs
○ 2019-03-23 21:12:32
○ 2026-03-27 16:42:42
○MXsmtp.secureserver.net2017-03-19 → 2017-03-19 · 3 obs
○ 2019-03-23 21:12:32
○ 2026-03-27 16:42:42
○A184.168.221.482017-03-19 → 2017-03-19 · 3 obs
○ 2019-03-23 21:12:32
○ 2026-03-27 16:42:42
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | f.gtld-servers.net, g.gtld-servers.net, h.gtld-servers.net, i.gtld-servers.net... | - |
| bridgle.com | ns-cloud-a1.googledomains.com, ns-cloud-a2.googledomains.com, ns-cloud-a3.googledomains.com, ns-cloud-a4.googledomains.com | 8 records |
✅ Authoritative Response
Server:216.239.32.106
NS records: ns-cloud-a1.googledomains.com, ns-cloud-a2.googledomains.com, ns-cloud-a3.googledomains.com, ns-cloud-a4.googledomains.com
🔒 DNSSEC Status
🔐 Secure (DNSSEC validated)
Chain of trust verified from root to domain
⏱️ Timing
Total: 373ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| NS | 4 | ns-cloud-a4.googledomains.com, ns-cloud-a1.googledomains.com... |
| SOA | 1 | ns-cloud-a1.googledomains.com cloud-dns- |
📌 Glue Records Collected
Total: 8
Out-of-bailiwick: 8 (ns-cloud-a1.googledomains.com, ns-cloud-a1.googledomains.com, ns-cloud-a2.googledomains.com...)
Analysis
Name Servers
bridgle.com is delegated to four name servers: ns-cloud-a1.googledomains.com, ns-cloud-a2.googledomains.com, ns-cloud-a3.googledomains.com and ns-cloud-a4.googledomains.com.
bridgle.com shares name servers with other domains at least partially, for instance siestakeyjuniors.com, sfa-us.com, victafro.com, pilatesstudioa.com and mystical-insites.com.
Host names with two IP numbers:
ns-cloud-a1.googledomains.com resolves to 2001:4860:4802:32::6a and 216.239.32.106.
ns-cloud-a2.googledomains.com resolves to 2001:4860:4802:34::6a and 216.239.34.106.
ns-cloud-a3.googledomains.com resolves to 2001:4860:4802:36::6a and 216.239.36.106.
ns-cloud-a4.googledomains.com resolves to 2001:4860:4802:38::6a and 216.239.38.106.