future-attack.de - robtex.com
future-attack.de
| DNSSEC | ⚠️ Not signed | ||||||
| A | 78.47.106.64🇩🇪 Hetzner78.46.0.0/15 HETZNER-RZ-NBG-BLK5 | ||||||
| PTR | static.64.106.47.78.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-04-23 #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=1775191212 | ||||||
Subdomains
www.future-attack.de |
Same first word
future-attack.de |
DNS History
19 records (3 active, 16 former)
○NSns.metro-ag.com2015-08-11 → 2017-03-23 · 4 obs
● 2015-08-11 19:19:42
● 2017-03-23 10:00:48
○ 2020-02-29 03:11:46
○ 2026-04-03 04:46:24
● 2017-03-23 10:00:48
○ 2020-02-29 03:11:46
○ 2026-04-03 04:46:24
○NSns.metro.de2015-08-11 → 2017-03-23 · 4 obs
● 2015-08-11 19:19:42
● 2017-03-23 10:00:48
○ 2020-02-29 03:11:46
○ 2026-04-03 04:46:24
● 2017-03-23 10:00:48
○ 2020-02-29 03:11:46
○ 2026-04-03 04:46:24
○NSns.metro.info2015-08-11 → 2017-03-23 · 4 obs
● 2015-08-11 19:19:42
● 2017-03-23 10:00:48
○ 2020-02-29 03:11:46
○ 2026-04-03 04:46:24
● 2017-03-23 10:00:48
○ 2020-02-29 03:11:46
○ 2026-04-03 04:46:24
○NSns.mgi.de2015-08-11 → 2017-03-23 · 4 obs
● 2015-08-11 19:19:42
● 2017-03-23 10:00:48
○ 2020-02-29 03:11:46
○ 2026-04-03 04:46:24
● 2017-03-23 10:00:48
○ 2020-02-29 03:11:46
○ 2026-04-03 04:46:24
●NSns1.redirectdom.com2026-03-29 → 2026-04-03 · 3 obs
○ 2020-02-29 03:11:46
● 2026-03-29 00:19:40
● 2026-04-03 04:46:24
● 2026-03-29 00:19:40
● 2026-04-03 04:46:24
○NSns1.sedoparking.com2020-02-29 → 2020-02-29 · 4 obs
○ 2017-03-23 10:00:48
● 2020-02-29 03:11:46
○ 2026-03-29 00:19:40
○ 2026-04-03 04:46:24
● 2020-02-29 03:11:46
○ 2026-03-29 00:19:40
○ 2026-04-03 04:46:24
●NSns2.redirectdom.com2026-03-29 → 2026-04-03 · 3 obs
○ 2020-02-29 03:11:46
● 2026-03-29 00:19:40
● 2026-04-03 04:46:24
● 2026-03-29 00:19:40
● 2026-04-03 04:46:24
○NSns2.sedoparking.com2020-02-29 → 2020-02-29 · 4 obs
○ 2017-03-23 10:00:48
● 2020-02-29 03:11:46
○ 2026-03-29 00:19:40
○ 2026-04-03 04:46:24
● 2020-02-29 03:11:46
○ 2026-03-29 00:19:40
○ 2026-04-03 04:46:24
○MXesmtp.media-saturn.com2017-03-23 → 2017-03-23 · 4 obs
○ 2015-08-11 19:19:42
● 2017-03-23 10:00:48
○ 2020-02-29 03:11:46
○ 2026-04-03 04:46:24
● 2017-03-23 10:00:48
○ 2020-02-29 03:11:46
○ 2026-04-03 04:46:24
○MXesmtp2.media-saturn.com2017-03-23 → 2017-03-23 · 4 obs
○ 2015-08-11 19:19:42
● 2017-03-23 10:00:48
○ 2020-02-29 03:11:46
○ 2026-04-03 04:46:24
● 2017-03-23 10:00:48
○ 2020-02-29 03:11:46
○ 2026-04-03 04:46:24
○MXesmtp3.media-saturn.com2017-03-23 → 2017-03-23 · 4 obs
○ 2015-08-11 19:19:42
● 2017-03-23 10:00:48
○ 2020-02-29 03:11:46
○ 2026-04-03 04:46:24
● 2017-03-23 10:00:48
○ 2020-02-29 03:11:46
○ 2026-04-03 04:46:24
○MXesmtp4.media-saturn.com2017-03-23 → 2017-03-23 · 4 obs
○ 2015-08-11 19:19:42
● 2017-03-23 10:00:48
○ 2020-02-29 03:11:46
○ 2026-04-03 04:46:24
● 2017-03-23 10:00:48
○ 2020-02-29 03:11:46
○ 2026-04-03 04:46:24
○MXinfogate.media-saturn.com2015-08-11 → 2017-03-23 · 4 obs
● 2015-08-11 19:19:42
● 2017-03-23 10:00:48
○ 2020-02-29 03:11:46
○ 2026-04-03 04:46:24
● 2017-03-23 10:00:48
○ 2020-02-29 03:11:46
○ 2026-04-03 04:46:24
○MXinfogate2.media-saturn.com2015-08-11 → 2017-03-23 · 4 obs
● 2015-08-11 19:19:42
● 2017-03-23 10:00:48
○ 2020-02-29 03:11:46
○ 2026-04-03 04:46:24
● 2017-03-23 10:00:48
○ 2020-02-29 03:11:46
○ 2026-04-03 04:46:24
○MXinfogate3.media-saturn.com2015-08-11 → 2017-03-23 · 4 obs
● 2015-08-11 19:19:42
● 2017-03-23 10:00:48
○ 2020-02-29 03:11:46
○ 2026-04-03 04:46:24
● 2017-03-23 10:00:48
○ 2020-02-29 03:11:46
○ 2026-04-03 04:46:24
○MXmail.pickelhost.com2020-02-29 → 2020-02-29 · 4 obs
○ 2017-03-23 10:00:48
● 2020-02-29 03:11:46
○ 2026-03-29 00:19:40
○ 2026-04-03 04:46:24
● 2020-02-29 03:11:46
○ 2026-03-29 00:19:40
○ 2026-04-03 04:46:24
○A194.233.193.942016-03-05 → 2017-03-23 · 4 obs
● 2016-03-05 22:06:36
● 2017-03-23 10:00:48
○ 2020-02-29 03:11:46
○ 2026-04-03 04:46:24
● 2017-03-23 10:00:48
○ 2020-02-29 03:11:46
○ 2026-04-03 04:46:24
●A78.47.106.642026-03-29 → 2026-04-03 · 3 obs
○ 2020-02-29 03:11:46
● 2026-03-29 00:19:40
● 2026-04-03 04:46:24
● 2026-03-29 00:19:40
● 2026-04-03 04:46:24
○A91.195.240.1262020-02-29 → 2020-02-29 · 4 obs
○ 2017-03-23 10:00:48
● 2020-02-29 03:11:46
○ 2026-03-29 00:19:40
○ 2026-04-03 04:46:24
● 2020-02-29 03:11:46
○ 2026-03-29 00:19:40
○ 2026-04-03 04:46:24
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| de | f.nic.de, z.nic.de, a.nic.de | - |
| future-attack.de | ns1.redirectdom.com, ns2.redirectdom.com | - |
✅ Authoritative Response
Server:168.119.46.105
NS records: ns1.redirectdom.com, ns2.redirectdom.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for future-attack.de (unsigned zone)
⏱️ Timing
Total: 1418ms | 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
www.future-attack.de has future-attack.de as its parent.
IP Addresses
future-attack.de maps to IP address 78.47.106.64.
Other host names, for instance c13-b2b-blog-lb.24www.jackenmoncleroutlet.de, microscale.de, mail.parts-hub.de, austg.de and makurat.de share IP numbers with future-attack.de.
Name Servers
Two name servers ns1.redirectdom.com and ns2.redirectdom.com are delegated to future-attack.de.
future-attack.de uses the same name server configuration as other domains, such as onlinetrip.de, gravas.de, friseurteam-lemke.de, mrdon.de and recolor.de.
Host names with a single IP address:
ns1.redirectdom.com points to 168.119.46.105
ns2.redirectdom.com points to 51.195.125.195