javamuseum.de - robtex.com
javamuseum.de
| DNSSEC | ⚠️ Not signed | ||||||
| A | 23.88.34.196🇩🇪 Hetzner23.88.0.0/17 HETZNER-DC | ||||||
| PTR | static.196.34.88.23.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 2025-05-08 #2 | ||||||
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=1785697994 | ||||||
Subdomains
www.javamuseum.de |
Same first word
javamuseum.de |
DNS History
17 records (3 active, 14 former)
○NSns.domeinguru.nl2015-10-20 → 2016-04-09 · 5 obs
● 2015-10-20 23:40:52
● 2016-04-09 23:18:18
○ 2016-12-23 06:43:08
○ 2026-08-02 19:49:08
○NSns1.domainname.at2017-12-16 → 2017-12-16 · 4 obs
● 2017-12-16 04:48:54
○ 2026-04-07 04:54:22
○ 2026-08-02 19:49:08
○NSns1.domeinguru.nl2015-10-20 → 2016-04-09 · 5 obs
● 2015-10-20 23:40:52
● 2016-04-09 23:18:18
○ 2016-12-23 06:43:08
○ 2026-08-02 19:49:08
○NSns1.parkingcrew.net2015-05-31 → 2015-05-31 · 3 obs
○ 2015-10-20 23:40:52
○ 2026-08-02 19:49:08
●NSns1.redirectdom.com2017-12-16 → 2026-08-02 · 3 obs
● 2017-12-16 04:48:54
● 2026-08-02 19:49:08
○NSns1.sedoparking.com2016-12-23 → 2016-12-23 · 4 obs
● 2016-12-23 06:43:08
○ 2017-12-16 04:48:54
○ 2026-08-02 19:49:08
○NSns2.parkingcrew.net2015-05-31 → 2015-05-31 · 3 obs
○ 2015-10-20 23:40:52
○ 2026-08-02 19:49:08
●NSns2.redirectdom.com2017-12-16 → 2026-08-02 · 3 obs
● 2017-12-16 04:48:54
● 2026-08-02 19:49:08
○NSns2.sedoparking.com2016-12-23 → 2016-12-23 · 4 obs
● 2016-12-23 06:43:08
○ 2017-12-16 04:48:54
○ 2026-08-02 19:49:08
○MXlocalhost2016-12-23 → 2016-12-23 · 4 obs
● 2016-12-23 06:43:08
○ 2017-12-16 04:48:54
○ 2026-08-02 19:49:08
○MXmail.h-email.net2015-05-31 → 2015-05-31 · 3 obs
○ 2015-10-20 23:40:52
○ 2026-08-02 19:49:08
○MXmailfilter1.webguru.nl2015-10-20 → 2016-04-09 · 5 obs
● 2015-10-20 23:40:52
● 2016-04-09 23:18:18
○ 2016-12-23 06:43:08
○ 2026-08-02 19:49:08
○A176.9.83.2292017-12-16 → 2017-12-16 · 4 obs
● 2017-12-16 04:48:54
○ 2026-04-07 04:54:22
○ 2026-08-02 19:49:08
○A185.53.177.92015-05-31 → 2015-05-31 · 3 obs
○ 2015-10-20 23:40:52
○ 2026-08-02 19:49:08
○A213.132.197.182015-10-20 → 2016-04-09 · 5 obs
● 2015-10-20 23:40:52
● 2016-04-09 23:18:18
○ 2016-12-23 06:43:08
○ 2026-08-02 19:49:08
●A23.88.34.1962026-04-07 → 2026-08-02 · 3 obs
● 2026-04-07 04:54:22
● 2026-08-02 19:49:08
○A72.52.4.1212016-12-23 → 2016-12-23 · 4 obs
● 2016-12-23 06:43:08
○ 2017-12-16 04:48:54
○ 2026-08-02 19:49:08
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| de | a.nic.de, f.nic.de, z.nic.de | - |
| javamuseum.de | ns2.redirectdom.com, ns1.redirectdom.com | - |
✅ Authoritative Response
Server:51.195.125.195
NS records: ns2.redirectdom.com, ns1.redirectdom.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for javamuseum.de (unsigned zone)
⏱️ Timing
Total: 947ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 23.88.34.196 |
| NS | 2 | ns2.redirectdom.com, ns1.redirectdom.com |
| SOA | 1 | ns1.redirectdom.com dnsmaster.ns1.redire |
Analysis
Hierarchy
javamuseum.de is a parent domain of www.javamuseum.de.
IP Addresses
javamuseum.de directs to one IP number, which is 23.88.34.196.
Among the host names that share IP numbers with javamuseum.de are versite.de, leistungsanspruch.de, edinson.de and two others.
Name Servers
javamuseum.de has two authoritative name servers — ns1.redirectdom.com and ns2.redirectdom.com.
javamuseum.de has the same name server delegation as a number of other domains, such as proliga.de, randig.de, (0x7075737379)bat.de and two more.
ns1.redirectdom.com and ns2.redirectdom.com each resolve to one IP number: ns1.redirectdom.com points to 168.119.46.105 and ns2.redirectdom.com points to 51.195.125.195.