nosnetwork.de - dns.ninja
nosnetwork.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-11 #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=1785485955 | ||||||
Same first word
nosnetwork.de |
nosnetwork.com |
Similar names
newskontor.de |
nonetworks.com |
onsnetwork.com |
onnetworks.net |
tensorknow.com |
tenonworks.com |
sonnetwork.com |
newskontor.com |
sworntoken.xyz |
onnetworks.de |
nowstkreno.run |
onnetworks.com |
krownstone.com |
networkons.com |
DNS History
16 records (3 active, 13 former)
○NSns1.domainname.at2018-10-04 → 2018-10-04 · 4 obs
○ 2017-02-01 03:43:08
● 2018-10-04 18:48:14
○ 2026-03-15 02:01:18
○ 2026-07-31 08:21:18
● 2018-10-04 18:48:14
○ 2026-03-15 02:01:18
○ 2026-07-31 08:21:18
●NSns1.redirectdom.com2018-10-04 → 2026-07-31 · 3 obs
○ 2017-02-01 03:43:08
● 2018-10-04 18:48:14
● 2026-07-31 08:21:18
● 2018-10-04 18:48:14
● 2026-07-31 08:21:18
○NSns1.sedoparking.com2017-02-01 → 2017-02-01 · 4 obs
○ 2016-05-09 04:58:24
● 2017-02-01 03:43:08
○ 2018-10-04 18:48:14
○ 2026-07-31 08:21:18
● 2017-02-01 03:43:08
○ 2018-10-04 18:48:14
○ 2026-07-31 08:21:18
●NSns2.redirectdom.com2018-10-04 → 2026-07-31 · 3 obs
○ 2017-02-01 03:43:08
● 2018-10-04 18:48:14
● 2026-07-31 08:21:18
● 2018-10-04 18:48:14
● 2026-07-31 08:21:18
○NSns2.sedoparking.com2017-02-01 → 2017-02-01 · 4 obs
○ 2016-05-09 04:58:24
● 2017-02-01 03:43:08
○ 2018-10-04 18:48:14
○ 2026-07-31 08:21:18
● 2017-02-01 03:43:08
○ 2018-10-04 18:48:14
○ 2026-07-31 08:21:18
○NSns65.1und1.de2015-07-16 → 2016-05-09 · 4 obs
● 2015-07-16 14:55:16
● 2016-05-09 04:58:24
○ 2017-02-01 03:43:08
○ 2026-07-31 08:21:18
● 2016-05-09 04:58:24
○ 2017-02-01 03:43:08
○ 2026-07-31 08:21:18
○NSns66.1und1.de2015-07-16 → 2016-05-09 · 4 obs
● 2015-07-16 14:55:16
● 2016-05-09 04:58:24
○ 2017-02-01 03:43:08
○ 2026-07-31 08:21:18
● 2016-05-09 04:58:24
○ 2017-02-01 03:43:08
○ 2026-07-31 08:21:18
○MXlocalhost2017-02-01 → 2017-02-01 · 4 obs
○ 2016-05-09 04:58:24
● 2017-02-01 03:43:08
○ 2018-10-04 18:48:14
○ 2026-07-31 08:21:18
● 2017-02-01 03:43:08
○ 2018-10-04 18:48:14
○ 2026-07-31 08:21:18
○MXmx00.kundenserver.de2015-07-16 → 2016-05-09 · 4 obs
● 2015-07-16 14:55:16
● 2016-05-09 04:58:24
○ 2017-02-01 03:43:08
○ 2026-07-31 08:21:18
● 2016-05-09 04:58:24
○ 2017-02-01 03:43:08
○ 2026-07-31 08:21:18
○MXmx01.kundenserver.de2015-07-16 → 2016-05-09 · 4 obs
● 2015-07-16 14:55:16
● 2016-05-09 04:58:24
○ 2017-02-01 03:43:08
○ 2026-07-31 08:21:18
● 2016-05-09 04:58:24
○ 2017-02-01 03:43:08
○ 2026-07-31 08:21:18
○MXstatic.51.2.69.159.clients.your-server.de2018-10-04 → 2018-10-04 · 4 obs
○ 2017-02-01 03:43:08
● 2018-10-04 18:48:14
○ 2026-03-15 02:01:18
○ 2026-07-31 08:21:18
● 2018-10-04 18:48:14
○ 2026-03-15 02:01:18
○ 2026-07-31 08:21:18
○A176.9.83.2292018-10-04 → 2018-10-04 · 4 obs
○ 2017-02-01 03:43:08
● 2018-10-04 18:48:14
○ 2026-03-15 02:01:18
○ 2026-07-31 08:21:18
● 2018-10-04 18:48:14
○ 2026-03-15 02:01:18
○ 2026-07-31 08:21:18
○A217.160.231.2422016-05-09 → 2016-05-09 · 4 obs
○ 2016-02-25 19:10:14
● 2016-05-09 04:58:24
○ 2017-02-01 03:43:08
○ 2026-07-31 08:21:18
● 2016-05-09 04:58:24
○ 2017-02-01 03:43:08
○ 2026-07-31 08:21:18
●A23.88.34.1962026-03-15 → 2026-07-31 · 3 obs
○ 2018-10-04 18:48:14
● 2026-03-15 02:01:18
● 2026-07-31 08:21:18
● 2026-03-15 02:01:18
● 2026-07-31 08:21:18
○A72.52.4.912017-02-01 → 2017-02-01 · 4 obs
○ 2016-05-09 04:58:24
● 2017-02-01 03:43:08
○ 2018-10-04 18:48:14
○ 2026-07-31 08:21:18
● 2017-02-01 03:43:08
○ 2018-10-04 18:48:14
○ 2026-07-31 08:21:18
○A82.165.113.372015-07-16 → 2016-02-25 · 4 obs
● 2015-07-16 14:55:16
● 2016-02-25 19:10:14
○ 2016-05-09 04:58:24
○ 2026-07-31 08:21:18
● 2016-02-25 19:10:14
○ 2016-05-09 04:58:24
○ 2026-07-31 08:21:18
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| de | a.nic.de, f.nic.de, z.nic.de | - |
| nosnetwork.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 nosnetwork.de (unsigned zone)
⏱️ Timing
Total: 931ms | 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
IP Addresses
nosnetwork.de has exactly one IP address — 23.88.34.196.
akelm.de, ipera.de, autoguard.de plus two other host names have IP numbers in common with nosnetwork.de.
Name Servers
DNS delegation for nosnetwork.de points to two name servers: ns1.redirectdom.com and ns2.redirectdom.com.
The name server configuration of nosnetwork.de is shared with other domains, for instance motosportfotografie.de, cellip.de, aris-personal.de and two others.
ns1.redirectdom.com → 168.119.46.105 and ns2.redirectdom.com → 51.195.125.195: one IP number per host name.