devicelock.de - dns.ninja
devicelock.de
| DNSSEC | ⚠️ Not signed | ||||||
| A | 78.47.106.64Hetzner78.46.0.0/15 | ||||||
| NS | ns1.redirectdom.com ⭐ | ||||||
| A | 168.119.46.105Hetzner168.119.0.0/16 | ||||||
| NS | ns2.redirectdom.com | ||||||
| A | 51.195.125.195 | ||||||
| SOA | ns1.redirectdom.comdnsmaster@ns1.redirectdom.com 2025-10-25 #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=1783596443 | ||||||
Subdomains
Same first word
Similar names
DNS History
16 records (3 active, 13 former)
○NSns1.first-ns.de2015-05-18 → 2017-03-28 · 4 obs
● 2015-05-18 10:58:54
● 2017-03-28 12:12:20
○ 2020-01-22 20:08:38
○ 2026-07-09 11:45:56
● 2017-03-28 12:12:20
○ 2020-01-22 20:08:38
○ 2026-07-09 11:45:56
●NSns1.redirectdom.com2026-02-17 → 2026-07-09 · 3 obs
○ 2020-01-22 20:08:38
● 2026-02-17 06:45:44
● 2026-07-09 11:45:56
● 2026-02-17 06:45:44
● 2026-07-09 11:45:56
●NSns2.redirectdom.com2026-02-17 → 2026-07-09 · 3 obs
○ 2020-01-22 20:08:38
● 2026-02-17 06:45:44
● 2026-07-09 11:45:56
● 2026-02-17 06:45:44
● 2026-07-09 11:45:56
○NSns5.gpesos.de2020-01-22 → 2020-01-22 · 4 obs
○ 2017-03-28 12:12:20
● 2020-01-22 20:08:38
○ 2026-02-17 06:45:44
○ 2026-07-09 11:45:56
● 2020-01-22 20:08:38
○ 2026-02-17 06:45:44
○ 2026-07-09 11:45:56
○NSns6.goeppel.eu2020-01-22 → 2020-01-22 · 4 obs
○ 2017-03-28 12:12:20
● 2020-01-22 20:08:38
○ 2026-02-17 06:45:44
○ 2026-07-09 11:45:56
● 2020-01-22 20:08:38
○ 2026-02-17 06:45:44
○ 2026-07-09 11:45:56
○NSns7.goeppel.eu2020-01-22 → 2020-01-22 · 4 obs
○ 2017-03-28 12:12:20
● 2020-01-22 20:08:38
○ 2026-02-17 06:45:44
○ 2026-07-09 11:45:56
● 2020-01-22 20:08:38
○ 2026-02-17 06:45:44
○ 2026-07-09 11:45:56
○NSrobotns2.second-ns.de2015-05-18 → 2017-03-28 · 4 obs
● 2015-05-18 10:58:54
● 2017-03-28 12:12:20
○ 2020-01-22 20:08:38
○ 2026-07-09 11:45:56
● 2017-03-28 12:12:20
○ 2020-01-22 20:08:38
○ 2026-07-09 11:45:56
○NSrobotns3.second-ns.com2015-05-18 → 2017-03-28 · 4 obs
● 2015-05-18 10:58:54
● 2017-03-28 12:12:20
○ 2020-01-22 20:08:38
○ 2026-07-09 11:45:56
● 2017-03-28 12:12:20
○ 2020-01-22 20:08:38
○ 2026-07-09 11:45:56
○MXmail.devicelock.de2015-05-18 → 2016-03-23 · 4 obs
● 2015-05-18 10:58:54
● 2016-03-23 23:06:58
○ 2016-08-08 06:25:08
○ 2026-07-09 11:45:56
● 2016-03-23 23:06:58
○ 2016-08-08 06:25:08
○ 2026-07-09 11:45:56
○MXmail2.devicelock.de2016-08-08 → 2017-03-28 · 5 obs
○ 2016-03-23 23:06:58
● 2016-08-08 06:25:08
● 2017-03-28 12:12:20
○ 2020-01-22 20:08:38
○ 2026-07-09 11:45:56
● 2016-08-08 06:25:08
● 2017-03-28 12:12:20
○ 2020-01-22 20:08:38
○ 2026-07-09 11:45:56
○MXmail3.devicelock.de2020-01-22 → 2026-02-17 · 5 obs
○ 2017-03-28 12:12:20
● 2020-01-22 20:08:38
● 2026-02-17 06:45:44
○ 2026-03-06 11:30:20
○ 2026-07-09 11:45:56
● 2020-01-22 20:08:38
● 2026-02-17 06:45:44
○ 2026-03-06 11:30:20
○ 2026-07-09 11:45:56
○MXmail3.goeppel.eu2020-01-22 → 2026-02-17 · 5 obs
○ 2017-03-28 12:12:20
● 2020-01-22 20:08:38
● 2026-02-17 06:45:44
○ 2026-03-06 11:30:20
○ 2026-07-09 11:45:56
● 2020-01-22 20:08:38
● 2026-02-17 06:45:44
○ 2026-03-06 11:30:20
○ 2026-07-09 11:45:56
○A136.243.76.1902016-03-23 → 2017-03-28 · 5 obs
○ 2015-12-27 21:38:06
● 2016-03-23 23:06:58
● 2017-03-28 12:12:20
○ 2020-01-22 20:08:38
○ 2026-07-09 11:45:56
● 2016-03-23 23:06:58
● 2017-03-28 12:12:20
○ 2020-01-22 20:08:38
○ 2026-07-09 11:45:56
○A213.83.7.442015-05-18 → 2015-12-27 · 4 obs
● 2015-05-18 10:58:54
● 2015-12-27 21:38:06
○ 2016-03-23 23:06:58
○ 2026-07-09 11:45:56
● 2015-12-27 21:38:06
○ 2016-03-23 23:06:58
○ 2026-07-09 11:45:56
●A78.47.106.642026-02-17 → 2026-07-09 · 3 obs
○ 2020-01-22 20:08:38
● 2026-02-17 06:45:44
● 2026-07-09 11:45:56
● 2026-02-17 06:45:44
● 2026-07-09 11:45:56
○A88.99.222.432020-01-22 → 2020-01-22 · 4 obs
○ 2017-03-28 12:12:20
● 2020-01-22 20:08:38
○ 2026-02-17 06:45:44
○ 2026-07-09 11:45:56
● 2020-01-22 20:08:38
○ 2026-02-17 06:45:44
○ 2026-07-09 11:45:56
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| de | a.nic.de, f.nic.de, z.nic.de | - |
| devicelock.de | ns1.redirectdom.com, ns2.redirectdom.com | - |
✅ Authoritative Response
Server:51.195.125.195
NS records: ns1.redirectdom.com, ns2.redirectdom.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for devicelock.de (unsigned zone)
⏱️ Timing
Total: 1385ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 78.47.106.64 |
| NS | 2 | ns2.redirectdom.com, ns1.redirectdom.com |
| SOA | 1 | ns1.redirectdom.com dnsmaster.ns1.redire |
Analysis
Hierarchy
mail2.devicelock.de, mail3.devicelock.de and mail.devicelock.de are all subdomains of devicelock.de.
IP Addresses
devicelock.de directs to one IP number, which is 78.47.106.64.
Name Servers
Two name servers handle the delegation for devicelock.de: ns1.redirectdom.com and ns2.redirectdom.com.
Both ns1.redirectdom.com and ns2.redirectdom.com have a single IP address each — ns1.redirectdom.com resolves to 168.119.46.105 while ns2.redirectdom.com resolves to 51.195.125.195.