brideparade.com - robtex.com
brideparade.com
| DNSSEC | ⚠️ Not signed | ||||||
| NS | ns25.domaincontrol.com ⚠️ Not in zone NS records | ||||||
| A | 2603:5:2161::d🇺🇸 GODADDY-DNS2603:5:2160::/44 | ||||||
| PTR | ns25.domaincontrol.com | ||||||
| A | 97.74.102.13🇺🇸 GODADDY-DNS97.74.102.0/23 | ||||||
| PTR | ns25.domaincontrol.com | ||||||
| NS | ns26.domaincontrol.com ⚠️ Not in zone NS records | ||||||
| A | 2603:5:2261::d🇺🇸 GODADDY-DNS2603:5:2260::/44 | ||||||
| PTR | ns26.domaincontrol.com | ||||||
| A | 173.201.70.13🇺🇸 GODADDY-DNS173.201.70.0/23 | ||||||
| PTR | ns26.domaincontrol.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=1774516927 | ||||||
Same first word
brideparade.com |
DNS History
6 records (2 active, 4 former)
○NSns10.schlundtech.de2008-03-15 → 2008-03-15 · 3 obs
● 2008-03-15 11:17:44
○ 2015-10-28 14:04:52
○ 2026-03-26 09:46:02
○ 2015-10-28 14:04:52
○ 2026-03-26 09:46:02
●NSns25.domaincontrol.com2026-03-11 → 2026-03-26 · 3 obs
○ 2015-10-28 14:04:52
● 2026-03-11 00:48:08
● 2026-03-26 09:46:02
● 2026-03-11 00:48:08
● 2026-03-26 09:46:02
●NSns26.domaincontrol.com2026-03-11 → 2026-03-26 · 3 obs
○ 2015-10-28 14:04:52
● 2026-03-11 00:48:08
● 2026-03-26 09:46:02
● 2026-03-11 00:48:08
● 2026-03-26 09:46:02
○NSns9.schlundtech.de2008-03-15 → 2008-03-15 · 3 obs
● 2008-03-15 11:17:44
○ 2015-10-28 14:04:52
○ 2026-03-26 09:46:02
○ 2015-10-28 14:04:52
○ 2026-03-26 09:46:02
○MXp15191067.pureserver.info2008-03-15 → 2008-03-15 · 3 obs
● 2008-03-15 11:17:44
○ 2015-10-28 14:04:52
○ 2026-03-26 09:46:02
○ 2015-10-28 14:04:52
○ 2026-03-26 09:46:02
○A212.227.90.1342008-03-15 → 2008-03-15 · 3 obs
● 2008-03-15 11:17:44
○ 2015-10-28 14:04:52
○ 2026-03-26 09:46:02
○ 2015-10-28 14:04:52
○ 2026-03-26 09:46:02
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | l.gtld-servers.net, j.gtld-servers.net, h.gtld-servers.net, d.gtld-servers.net... | - |
| brideparade.com | ns25.domaincontrol.com, ns26.domaincontrol.com | 4 records |
✅ Authoritative Response
Server:97.74.102.13
NS records: ns25.domaincontrol.com, ns26.domaincontrol.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for brideparade.com (unsigned zone)
⏱️ Timing
Total: 95ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|
📌 Glue Records Collected
Total: 4
Out-of-bailiwick: 4 (ns25.domaincontrol.com, ns25.domaincontrol.com, ns26.domaincontrol.com...)
Analysis
Name Servers
brideparade.com is delegated to two name servers: ns25.domaincontrol.com and ns26.domaincontrol.com.
brideparade.com uses the same name server setup as other domains such as cjdiamonds.co, elkan.com, nutxr.com, vryz.com and gesswork.com.
Host names with two IP numbers:
ns25.domaincontrol.com points to 2603:5:2161::d and 97.74.102.13; ns26.domaincontrol.com points to 2603:5:2261::d and 173.201.70.13.