bilgewatch.de - robtex.com
bilgewatch.de
| DNSSEC | ⚠️ Not signed | ||||||
| A | 162.55.40.124🇩🇪 Hetzner162.55.0.0/16 HETZNER-DC | ||||||
| PTR | static.124.40.55.162.clients.your-server.de | ||||||
| NS | ns1.redirectdom.com ⭐ | ||||||
| A | 168.119.46.105🇩🇪 Hetzner168.119.0.0/16 HETZNER-DC | ||||||
| PTR | ns1.redirectdom.com | ||||||
| NS | ns2.redirectdom.com | ||||||
| A | 51.195.125.195🇫🇷 OVH51.195.0.0/16 | ||||||
| PTR | ns2.redirectdom.com | ||||||
| SOA | ns1.redirectdom.comdnsmaster@ns1.redirectdom.com 2026-06-06 #20 | ||||||
de
| DNSSEC | 🔒 Signed (DS record present) | ||||||
| NS | f.nic.de ⭐ | ||||||
| NS | a.nic.de | ||||||
| NS | l.de.net ⚠️ Not in parent delegation | ||||||
| NS | n.de.net ⚠️ Not in parent delegation | ||||||
| NS | s.de.net ⚠️ Not in parent delegation | ||||||
| NS | z.nic.de | ||||||
| SOA | f.nic.dedns-operations@denic.de serial=1784291185 | ||||||
Previously MX for
bilgewatch.de |
Same first word
bilgewatch.de |
Similar names
DNS History
9 records (3 active, 6 former)
○NSns1.domainzentrale.eu2015-06-30 → 2016-04-25 · 4 obs
● 2016-04-25 23:39:16
○ 2026-03-24 04:13:28
○ 2026-07-17 12:36:32
●NSns1.redirectdom.com2026-03-24 → 2026-07-17 · 3 obs
● 2026-03-24 04:13:28
● 2026-07-17 12:36:32
○NSns2.domainzentrale.eu2015-06-30 → 2016-04-25 · 4 obs
● 2016-04-25 23:39:16
○ 2026-03-24 04:13:28
○ 2026-07-17 12:36:32
●NSns2.redirectdom.com2026-03-24 → 2026-07-17 · 3 obs
● 2026-03-24 04:13:28
● 2026-07-17 12:36:32
○NSns3.domainzentrale.eu2015-06-30 → 2016-04-25 · 4 obs
● 2016-04-25 23:39:16
○ 2026-03-24 04:13:28
○ 2026-07-17 12:36:32
○NSns4.domainzentrale.eu2015-06-30 → 2016-04-25 · 4 obs
● 2016-04-25 23:39:16
○ 2026-03-24 04:13:28
○ 2026-07-17 12:36:32
○MXbilgewatch.de2015-06-30 → 2016-04-25 · 4 obs
● 2016-04-25 23:39:16
○ 2026-03-24 04:13:28
○ 2026-07-17 12:36:32
○A146.0.36.952015-06-30 → 2016-04-25 · 4 obs
● 2016-04-25 23:39:16
○ 2026-03-24 04:13:28
○ 2026-07-17 12:36:32
●A162.55.40.1242026-03-24 → 2026-07-17 · 3 obs
● 2026-03-24 04:13:28
● 2026-07-17 12:36:32
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| de | a.nic.de, f.nic.de, z.nic.de | - |
| bilgewatch.de | ns2.redirectdom.com, ns1.redirectdom.com | - |
✅ Authoritative Response
Server:168.119.46.105
NS records: ns2.redirectdom.com, ns1.redirectdom.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for bilgewatch.de (unsigned zone)
⏱️ Timing
Total: 2456ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 162.55.40.124 |
| NS | 2 | ns1.redirectdom.com, ns2.redirectdom.com |
| SOA | 1 | ns1.redirectdom.com dnsmaster.ns1.redire |
Analysis
IP Addresses
bilgewatch.de resolves to just one IP address, 162.55.40.124.
Two other host names, along with ingenico-healthcare.de, mail1.agi-nord.de and kamikaze-sushi.de, also share IP numbers with bilgewatch.de.
Name Servers
Two name servers handle the delegation for bilgewatch.de: ns1.redirectdom.com and ns2.redirectdom.com.
bilgewatch.de shares its NS records with other domains, for example fueloep.de, nagle.de, esspertin.de and two others.
ns1.redirectdom.com resolves to 168.119.46.105. ns2.redirectdom.com resolves to 51.195.125.195. Both host names point to a single IP number.