codering.nl - dns.ninja
codering.nl
| DNSSEC | β οΈ Not signed | ||||||
| A | 2604:a880:800:14:0:1:f06c:6000πΊπΈ DIGITALOCEAN2604:a880:800::/48 DigitalOcean | ||||||
| A | 134.199.240.162πΊπΈ DIGITALOCEAN134.199.240.0/20 DigitalOcean | ||||||
| NS | ns1.nameshift.com β | ||||||
| A | 2a13:9500:170::1π¬π§ AS229272000::/3 | ||||||
| A | 5.83.212.1π¬π§ ORG-SDL28-RIPE5.83.212.0/24 autogen | ||||||
| NS | lb9d7c.ns3.nameshift.com β οΈ Not in parent delegation | ||||||
| A | 2a13:9500:170::3π¬π§ AS229272000::/3 | ||||||
| A | 5.83.212.3π¬π§ ORG-SDL28-RIPE5.83.212.0/24 autogen | ||||||
| NS | ns2.nameshift.com | ||||||
| A | 2a13:9500:170::2π¬π§ AS229272000::/3 | ||||||
| A | 5.83.212.2π¬π§ ORG-SDL28-RIPE5.83.212.0/24 autogen | ||||||
| TXT | v=spf1 -all | ||||||
| SOA | ns1.nameshift.comhostmaster@nameshift.com serial=1781427600 | ||||||
nl
| DNSSEC | π Signed (DS record present) | ||||||
| NS | ns1.dns.nl β | ||||||
| NS | ns3.dns.nl | ||||||
| NS | ns4.dns.nl | ||||||
| TXT | nl zone update: 2026-06-14 09:00:01 +0000 (EPOCH 1781427601) | ||||||
| SOA | ns1.dns.nldns@sidn.nl 2026-06-14 #18 | ||||||
Same first word
Similar names
DNS History
17 records (5 active, 12 former)
βNSlb9d7c.ns3.nameshift.com2026-06-13 β 2026-06-14 Β· 3 obs
β 2026-06-13 05:32:44
β 2026-06-14 09:31:34
βNSns1.nameshift.com2026-06-13 β 2026-06-14 Β· 3 obs
β 2026-06-13 05:32:44
β 2026-06-14 09:31:34
βNSns2.nameshift.com2026-06-13 β 2026-06-14 Β· 3 obs
β 2026-06-13 05:32:44
β 2026-06-14 09:31:34
βNSnsauth1.bit.nl2015-06-22 β 2017-11-03 Β· 4 obs
β 2017-11-03 00:29:56
β 2026-06-13 05:32:44
β 2026-06-14 09:31:34
βNSnsauth2.bit.nl2015-06-22 β 2017-11-03 Β· 4 obs
β 2017-11-03 00:29:56
β 2026-06-13 05:32:44
β 2026-06-14 09:31:34
βNSnsauth3.bit.org2015-06-22 β 2017-11-03 Β· 4 obs
β 2017-11-03 00:29:56
β 2026-06-13 05:32:44
β 2026-06-14 09:31:34
βA134.199.240.1622026-06-14 β 2026-06-14 Β· 2 obs
β 2026-06-14 09:31:34
βA185.104.28.2382026-06-13 β 2026-06-14 Β· 2 obs
β 2026-06-14 09:31:34
βA2001:7b8:3:32:213:136:0:1882016-12-24 β 2017-11-03 Β· 5 obs
β 2016-12-24 08:12:56
β 2017-11-03 00:29:56
β 2026-06-13 05:32:44
β 2026-06-14 09:31:34
βA209.38.54.1912026-06-13 β 2026-06-13 Β· 3 obs
β 2026-06-13 05:32:44
β 2026-06-14 09:31:34
βA213.136.0.1882015-06-22 β 2017-11-03 Β· 4 obs
β 2017-11-03 00:29:56
β 2026-06-13 05:32:44
β 2026-06-14 09:31:34
βA2604:a880:800:14:0:1:f06c:60002026-06-14 β 2026-06-14 Β· 2 obs
β 2026-06-14 09:31:34
βA2a03:b0c0:2:f0::fc3a:e0012026-06-13 β 2026-06-13 Β· 3 obs
β 2026-06-13 05:32:44
β 2026-06-14 09:31:34
βA2a06:2ec0:1::ffed2026-06-13 β 2026-06-14 Β· 2 obs
β 2026-06-14 09:31:34
π DNS Trace
π Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| nl | ns1.dns.nl, ns3.dns.nl, ns4.dns.nl | - |
| codering.nl | ns1.nameshift.com, ns2.nameshift.com | - |
β Authoritative Response
Server:5.83.212.2
NS records: ns1.nameshift.com, ns2.nameshift.com
π DNSSEC Status
β οΈ Insecure (no DNSSEC)
No DS record for codering.nl (unsigned zone)
β±οΈ Timing
Total: 335ms | Queries: -
π Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 134.199.240.162 |
| AAAA | 1 | 2604:a880:800:14:0:1:f06c:6000 |
| NS | 3 | ns1.nameshift.com, ns2.nameshift.com... |
| MX | 1 | . (pri: 0) |
| TXT | 1 | v=spf1 -all |
| SOA | 1 | ns1.nameshift.com hostmaster.nameshift.c |
Analysis
IP Addresses
codering.nl has two IP addresses: 134.199.240.162 and 2604:a880:800:14:0:1:f06c:6000
Among the host names that share IP numbers with codering.nl are zvp.be, www.(0x706f726e)oizle.eu, giftshops.eu and two others.
Name Servers
Three name servers are authoritative for codering.nl: ns1.nameshift.com, ns2.nameshift.com and lb9d7c.ns3.nameshift.com.
There is at least partial name server overlap between codering.nl and other domains β clag.eu, netx.fr, wbp.eu and two more among them.
These name servers are routinely co-deployed with the name servers xmhvxw.ns3.nameshift.com, poit15.ns3.nameshift.com, 1ux2f3.ns3.nameshift.com and two others.
ns1.nameshift.com resolves to 5.83.212.1 and 2a13:9500:170::1. ns2.nameshift.com resolves to 5.83.212.2 and 2a13:9500:170::2. lb9d7c.ns3.nameshift.com resolves to 5.83.212.3 and 2a13:9500:170::3. All three hostnames point to two IP numbers each.