funload.de - dns.ninja
funload.de
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=1782678619 | ||||||
Same first word
Similar names
DNS History
16 records (9 active, 7 former)
○NSns1.dp-media.de2015-08-17 → 2016-12-25 · 4 obs
● 2016-12-25 11:40:22
○ 2026-02-17 16:50:56
○ 2026-06-28 21:01:08
●NSns1.eu.rrpproxy.net2026-02-17 → 2026-06-28 · 3 obs
● 2026-02-17 16:50:56
● 2026-06-28 21:01:08
●NSns1.na.rrpproxy.net2026-02-17 → 2026-06-28 · 3 obs
● 2026-02-17 16:50:56
● 2026-06-28 21:01:08
●NSns1.rrpproxy.net2026-02-17 → 2026-06-28 · 3 obs
● 2026-02-17 16:50:56
● 2026-06-28 21:01:08
○NSns2.dp-media.de2015-08-17 → 2016-12-25 · 4 obs
● 2016-12-25 11:40:22
○ 2026-02-17 16:50:56
○ 2026-06-28 21:01:08
●NSns2.eu.rrpproxy.net2026-02-17 → 2026-06-28 · 3 obs
● 2026-02-17 16:50:56
● 2026-06-28 21:01:08
○NSns3.dp-media.de2015-08-17 → 2016-12-25 · 4 obs
● 2016-12-25 11:40:22
○ 2026-02-17 16:50:56
○ 2026-06-28 21:01:08
●MXalt1.aspmx.l.google.com2016-01-09 → 2026-06-28 · 3 obs
● 2016-01-09 10:11:32
● 2026-06-28 21:01:08
●MXalt2.aspmx.l.google.com2016-01-09 → 2026-06-28 · 3 obs
● 2016-01-09 10:11:32
● 2026-06-28 21:01:08
●MXaspmx.l.google.com2016-01-09 → 2026-06-28 · 3 obs
● 2016-01-09 10:11:32
● 2026-06-28 21:01:08
●MXaspmx2.googlemail.com2016-01-09 → 2026-06-28 · 3 obs
● 2016-01-09 10:11:32
● 2026-06-28 21:01:08
●MXaspmx3.googlemail.com2016-01-09 → 2026-06-28 · 3 obs
● 2016-01-09 10:11:32
● 2026-06-28 21:01:08
○MXpost.giga.de2015-08-17 → 2015-12-21 · 4 obs
● 2015-12-21 00:25:04
○ 2016-01-09 10:11:32
○ 2026-06-28 21:01:08
○A178.19.72.102016-12-09 → 2016-12-25 · 5 obs
● 2016-12-09 11:02:32
● 2016-12-25 11:40:22
○ 2026-02-17 16:50:56
○ 2026-06-28 21:01:08
○A46.253.113.1702026-02-17 → 2026-04-28 · 5 obs
● 2026-02-17 16:50:56
● 2026-04-28 04:21:34
○ 2026-05-08 04:04:04
○ 2026-06-28 21:01:08
○A80.86.80.1682015-08-17 → 2016-09-29 · 4 obs
● 2016-09-29 13:10:16
○ 2016-12-09 11:02:32
○ 2026-06-28 21:01:08
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| de | z.nic.de, a.nic.de, f.nic.de | - |
| funload.de | ns1.eu.rrpproxy.net, ns1.na.rrpproxy.net, ns2.eu.rrpproxy.net | - |
✅ Authoritative Response
Server:193.227.117.228
NS records: ns1.eu.rrpproxy.net, ns1.na.rrpproxy.net, ns2.eu.rrpproxy.net
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for funload.de (unsigned zone)
⏱️ Timing
Total: 1205ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| NS | 3 | ns1.eu.rrpproxy.net, ns1.na.rrpproxy.net... |
| MX | 5 | aspmx.l.google.com (pri: 1), alt1.aspmx.l.google.com (pri: 5)... |
| TXT | 1 | v=spf1 mx include:_spf.google.com -all |
| SOA | 1 | ns1.rrpproxy.net tech.key-systems.net |
Analysis
Name Servers
The domain funload.de is delegated to these four name servers: ns1.rrpproxy.net, ns1.eu.rrpproxy.net, ns2.eu.rrpproxy.net and ns1.na.rrpproxy.net.
The name servers of funload.de overlap at least partially with those of other domains — among them lalocanda.at, th2a.com, eipef.org and two more.
These name servers are routinely co-deployed with the name servers ns3.rrpproxy.net, ns2.rrpproxy.net, ns1.domaindiscount24.net and two others.
Each of the four hosts ns1.rrpproxy.net, ns1.eu.rrpproxy.net, ns2.eu.rrpproxy.net and ns1.na.rrpproxy.net has two IP addresses. ns1.rrpproxy.net points to 193.227.117.226 and 2a04:2b00:14cc::226. ns1.eu.rrpproxy.net points to 193.227.117.227 and 2a04:2b00:14cc::227. ns2.eu.rrpproxy.net points to 194.50.187.227 and 2a04:2b00:14dd::227. ns1.na.rrpproxy.net points to 193.227.117.228 and 2a04:2b00:14cc::228.
Mail Servers
Five mail servers handle funload.de: aspmx2.googlemail.com, aspmx3.googlemail.com, aspmx.l.google.com and two others.
funload.de shares at least some of its mail servers with other domains — for example ns500693.ns500693.ns500693.ns500734.ns500699.ns500734.ns500728.ns500699.ns500699.ns500693.ns500699.ns500612.ns500612.ns500578.ns500110.dtrkdll.com, ns500768.ns500759.ns500758.ns500758.ns500735.ns500735.ns500698.ns500708.ns500698.ns500576.ns500698.ns500708.ns500619.ns500652.trackreceptor.com, ns500742.ns500731.ns500742.ns500742.ns500742.ns500742.ns500705.ns500705.ns500705.ns500678.ns500666.ns500666.ns500153.tenderladiesbz.com and two more.
It is common to find these mail servers paired with mail servers alt1.aspmx.l.google.com, alt2.aspmx.l.google.com, alt3.aspmx.l.google.com and 3 more.
Hosts with two IP numbers each:
aspmx2.googlemail.com directs traffic to 108.177.123.26 and 2800:3f0:4003:c0f::1b.
aspmx3.googlemail.com directs traffic to 172.253.116.26 and 2a00:1450:400b:c02::1a.
aspmx.l.google.com directs traffic to 192.178.155.27 and 2607:f8b0:4004:c25::1a.
alt1.aspmx.l.google.com directs traffic to 108.177.123.27 and 2800:3f0:4003:c0f::1b.
alt2.aspmx.l.google.com directs traffic to 172.253.116.26 and 2a00:1450:400b:c02::1b.
Both aspmx2.googlemail.com and alt1.aspmx.l.google.com resolve to 2800:3f0:4003:c0f::1b IP addresses each.
Both aspmx3.googlemail.com and alt2.aspmx.l.google.com resolve to 172.253.116.26 IP addresses each.