weddingizer.com - robtex.com
weddingizer.com
| DNSSEC | ⚠️ Not signed | ||||||
| NS | ns1.catched.com ⚠️ Not in zone NS records | ||||||
| A | 116.203.52.191🇩🇪 Hetzner116.203.0.0/16 HETZNER-DC | ||||||
| PTR | static.191.52.203.116.clients.your-server.de | ||||||
| NS | ns2.catched.com ⚠️ Not in zone NS records | ||||||
| A | 116.203.26.124🇩🇪 Hetzner116.203.0.0/16 HETZNER-DC | ||||||
| PTR | static.124.26.203.116.clients.your-server.de | ||||||
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=1771291435 | ||||||
Same first word
weddingizer.com |
DNS History
14 records (2 active, 12 former)
○NSdns101.registrar-servers.com2026-03-23 → 2026-03-23 · 1 obs
○NSdns102.registrar-servers.com2026-03-23 → 2026-03-23 · 1 obs
○NSns1.arandomserver.com2021-11-07 → 2021-11-07 · 3 obs
● 2021-11-07 07:36:04
○ 2026-03-23 06:02:10
○NSns1.azeza.com2015-07-21 → 2016-05-14 · 4 obs
● 2016-05-14 15:49:18
○ 2021-11-07 07:36:04
○ 2026-03-23 06:02:10
●NSns1.catched.com2026-03-23 → 2026-03-23 · 2 obs
● 2026-03-23 06:02:10
○NSns2.arandomserver.com2021-11-07 → 2021-11-07 · 3 obs
● 2021-11-07 07:36:04
○ 2026-03-23 06:02:10
○NSns2.azeza.com2015-07-21 → 2016-05-14 · 4 obs
● 2016-05-14 15:49:18
○ 2021-11-07 07:36:04
○ 2026-03-23 06:02:10
●NSns2.catched.com2026-03-23 → 2026-03-23 · 2 obs
● 2026-03-23 06:02:10
○MXmx.plingest.com2026-03-23 → 2026-03-23 · 1 obs
○MXweddingizer.com2015-07-21 → 2021-11-07 · 3 obs
● 2021-11-07 07:36:04
○ 2026-03-23 06:02:10
○A172.234.24.2112026-03-23 → 2026-03-23 · 1 obs
○A172.239.57.1172026-03-23 → 2026-03-23 · 1 obs
○A172.245.255.1022015-07-21 → 2016-05-14 · 4 obs
● 2016-05-14 15:49:18
○ 2021-11-07 07:36:04
○ 2026-03-23 06:02:10
○A198.252.104.1412021-11-07 → 2021-11-07 · 3 obs
● 2021-11-07 07:36:04
○ 2026-03-23 06:02:10
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net... | - |
| weddingizer.com | ns1.catched.com, ns2.catched.com | 2 records |
✅ Authoritative Response
Server:116.203.52.191
NS records: ns1.catched.com, ns2.catched.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for weddingizer.com (unsigned zone)
⏱️ Timing
Total: 273ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|
📌 Glue Records Collected
Total: 2
Out-of-bailiwick: 2 (ns1.catched.com, ns2.catched.com)
Analysis
Name Servers
Two name servers ns1.catched.com and ns2.catched.com handle the delegation for weddingizer.com.
weddingizer.com shares the same name server setup as other domains, for example bookmo.org, josejavieresparza.es, excestore.nl, cafeterraza.com and testaenewsservice.com.
weddingizer.com at least partially shares name servers with other domains, for example banfootballz.com, nlist.fr, zonazero.es, casinopaysafecard.fr and peintureautopro.fr.
these name servers are commonly used with ns1.bodis.com, ns2.bodis.com, ns1.abovedomains.com, ns2.abovedomains.com, ns1.catcheddomains.com and ns2.catcheddomains.com.
Host names with one IP number:
ns1.catched.com points to 116.203.52.191; ns2.catched.com points to 116.203.26.124.