loadingdata.nl - dns.ninja
loadingdata.nl
| DNSSEC | ⚠️ Not signed | ||||||
| A | 2a03:b0c0:2:d0::ea2:6001DIGITALOCEAN2a03:b0c0:2::/48 | ||||||
| A | 206.189.0.178 | ||||||
| NS | ns1.digitalocean.com ⭐ | ||||||
| A | 2606:4700:52::ac40:34d2🇺🇸 Cloudflare2606:4700:52::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US | ||||||
| PTR | ns1.digitalocean.com | ||||||
| A | 172.64.52.210🇺🇸 Cloudflare172.64.52.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US | ||||||
| PTR | ns1.digitalocean.com | ||||||
| NS | ns2.digitalocean.com | ||||||
| A | 2606:4700:5a::ac40:3515🇺🇸 Cloudflare2606:4700:5a::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US | ||||||
| PTR | ns2.digitalocean.com | ||||||
| A | 172.64.53.21🇺🇸 Cloudflare172.64.53.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US | ||||||
| PTR | ns2.digitalocean.com | ||||||
| NS | ns3.digitalocean.com | ||||||
| A | 2606:4700:52::ac40:31d1🇺🇸 Cloudflare2606:4700:52::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US | ||||||
| PTR | ns3.digitalocean.com | ||||||
| A | 172.64.49.209🇺🇸 Cloudflare172.64.48.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US | ||||||
| PTR | ns3.digitalocean.com | ||||||
| SOA | ns1.digitalocean.comhostmaster@loadingdata.nl serial=0 | ||||||
nl
| DNSSEC | ⚠️ Not signed | ||||||
| NS | ns1.dns.nl ⭐ | ||||||
| NS | ns3.dns.nl | ||||||
| NS | ns4.dns.nl | ||||||
| TXT | nl zone update: 2026-10-31 18:30:01 +0000 (EPOCH 1793471401) | ||||||
| SOA | ns1.dns.nldns@sidn.nl 2026-10-31 #37 | ||||||
Same first word
loadingdata.org |
loadingdata.nl |
loadingdata.com |
Similar names
DNS History
14 records (5 active, 9 former)
●NSns1.digitalocean.com2026-08-19 → 2026-10-31 · 3 obs
○ 2017-03-28 09:40:56
● 2026-08-19 10:07:58
● 2026-10-31 19:31:44
● 2026-08-19 10:07:58
● 2026-10-31 19:31:44
●NSns2.digitalocean.com2026-08-19 → 2026-10-31 · 3 obs
○ 2017-03-28 09:40:56
● 2026-08-19 10:07:58
● 2026-10-31 19:31:44
● 2026-08-19 10:07:58
● 2026-10-31 19:31:44
●NSns3.digitalocean.com2026-08-19 → 2026-10-31 · 3 obs
○ 2017-03-28 09:40:56
● 2026-08-19 10:07:58
● 2026-10-31 19:31:44
● 2026-08-19 10:07:58
● 2026-10-31 19:31:44
○NSns3.domeinnaamreseller.nl2015-06-27 → 2017-03-28 · 4 obs
● 2015-06-27 23:18:40
● 2017-03-28 09:40:56
○ 2026-08-19 10:07:58
○ 2026-10-31 19:31:44
● 2017-03-28 09:40:56
○ 2026-08-19 10:07:58
○ 2026-10-31 19:31:44
○NSns4.domeinnaamreseller.nl2015-06-27 → 2017-03-28 · 4 obs
● 2015-06-27 23:18:40
● 2017-03-28 09:40:56
○ 2026-08-19 10:07:58
○ 2026-10-31 19:31:44
● 2017-03-28 09:40:56
○ 2026-08-19 10:07:58
○ 2026-10-31 19:31:44
○NSns5.domeinnaamreseller.nl2015-06-27 → 2017-03-28 · 4 obs
● 2015-06-27 23:18:40
● 2017-03-28 09:40:56
○ 2026-08-19 10:07:58
○ 2026-10-31 19:31:44
● 2017-03-28 09:40:56
○ 2026-08-19 10:07:58
○ 2026-10-31 19:31:44
○MXalt1.aspmx.l.google.com2015-06-27 → 2017-03-28 · 4 obs
● 2015-06-27 23:18:40
● 2017-03-28 09:40:56
○ 2026-08-19 10:07:58
○ 2026-10-31 19:31:44
● 2017-03-28 09:40:56
○ 2026-08-19 10:07:58
○ 2026-10-31 19:31:44
○MXalt2.aspmx.l.google.com2015-06-27 → 2017-03-28 · 4 obs
● 2015-06-27 23:18:40
● 2017-03-28 09:40:56
○ 2026-08-19 10:07:58
○ 2026-10-31 19:31:44
● 2017-03-28 09:40:56
○ 2026-08-19 10:07:58
○ 2026-10-31 19:31:44
○MXalt3.aspmx.l.google.com2015-06-27 → 2017-03-28 · 4 obs
● 2015-06-27 23:18:40
● 2017-03-28 09:40:56
○ 2026-08-19 10:07:58
○ 2026-10-31 19:31:44
● 2017-03-28 09:40:56
○ 2026-08-19 10:07:58
○ 2026-10-31 19:31:44
○MXalt4.aspmx.l.google.com2015-06-27 → 2017-03-28 · 4 obs
● 2015-06-27 23:18:40
● 2017-03-28 09:40:56
○ 2026-08-19 10:07:58
○ 2026-10-31 19:31:44
● 2017-03-28 09:40:56
○ 2026-08-19 10:07:58
○ 2026-10-31 19:31:44
○MXaspmx.l.google.com2015-06-27 → 2017-03-28 · 4 obs
● 2015-06-27 23:18:40
● 2017-03-28 09:40:56
○ 2026-08-19 10:07:58
○ 2026-10-31 19:31:44
● 2017-03-28 09:40:56
○ 2026-08-19 10:07:58
○ 2026-10-31 19:31:44
○A188.166.50.1152015-06-27 → 2017-03-28 · 4 obs
● 2015-06-27 23:18:40
● 2017-03-28 09:40:56
○ 2026-08-19 10:07:58
○ 2026-10-31 19:31:44
● 2017-03-28 09:40:56
○ 2026-08-19 10:07:58
○ 2026-10-31 19:31:44
●A206.189.0.1782026-08-19 → 2026-10-31 · 3 obs
○ 2017-03-28 09:40:56
● 2026-08-19 10:07:58
● 2026-10-31 19:31:44
● 2026-08-19 10:07:58
● 2026-10-31 19:31:44
●A2a03:b0c0:2:d0::ea2:60012026-08-19 → 2026-10-31 · 3 obs
○ 2017-03-28 09:40:56
● 2026-08-19 10:07:58
● 2026-10-31 19:31:44
● 2026-08-19 10:07:58
● 2026-10-31 19:31:44
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| nl | ns1.dns.nl, ns3.dns.nl, ns4.dns.nl | - |
| loadingdata.nl | ns1.digitalocean.com, ns2.digitalocean.com, ns3.digitalocean.com | - |
✅ Authoritative Response
Server:172.64.53.21
NS records: ns1.digitalocean.com, ns2.digitalocean.com, ns3.digitalocean.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
Root DNSKEY fetch failed: Error: connect EADDRNOTAVAIL 198.41.0.4:53 - Local (0.0.0.0:0)
⏱️ Timing
Total: 377ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 206.189.0.178 |
| AAAA | 1 | 2a03:b0c0:2:d0::ea2:6001 |
| NS | 3 | ns3.digitalocean.com, ns1.digitalocean.com... |
| SOA | 1 | ns1.digitalocean.com hostmaster.loadingd |
Analysis
IP Addresses
loadingdata.nl points to the IP addresses 206.189.0.178 and 2a03:b0c0:2:d0::ea2:6001
Name Servers
The authoritative name servers for loadingdata.nl are ns1.digitalocean.com, ns2.digitalocean.com and ns3.digitalocean.com — three in total.
ns1.digitalocean.com, ns2.digitalocean.com and ns3.digitalocean.com all resolve to exactly two IP numbers apiece: ns1.digitalocean.com → 172.64.52.210 and 2606:4700:52::ac40:34d2; ns2.digitalocean.com → 172.64.53.21 and 2606:4700:5a::ac40:3515; ns3.digitalocean.com → 172.64.49.209 and 2606:4700:52::ac40:31d1.