codesanctuary.com - dns.ninja
codesanctuary.com
| DNSSEC | ⚠️ Not signed | ||||||
| NS | ns1.dns-expired.com ⚠️ Not in zone NS records | ||||||
| A | 2a02:4780:27:abcd::34🇫🇷 IIHOS0012a02:4780:27::/48 HOSTINGER FR | ||||||
| A | 217.65.148.99🇬🇧 IIHOS001217.65.144.0/21 HOSTINGER FR | ||||||
| NS | ns2.dns-expired.com ⚠️ Not in zone NS records | ||||||
| A | 2a02:4780:b:abcd::d🇺🇸 IIHOS0012a02:4780:b::/48 HOSTINGER US | ||||||
| A | 217.21.79.21🇺🇸 IIHOS001217.21.76.0/22 HOSTINGER-US | ||||||
com
| DNSSEC | 🔒 Signed (DS record present) | ||||||
| NS | a.gtld-servers.net ⭐ | ||||||
| NS | b.gtld-servers.net | ||||||
| NS | c.gtld-servers.net | ||||||
| NS | d.gtld-servers.net | ||||||
| NS | e.gtld-servers.net | ||||||
| NS | f.gtld-servers.net | ||||||
| NS | g.gtld-servers.net | ||||||
| NS | h.gtld-servers.net | ||||||
| NS | i.gtld-servers.net | ||||||
| NS | j.gtld-servers.net | ||||||
| NS | k.gtld-servers.net | ||||||
| NS | l.gtld-servers.net | ||||||
| NS | m.gtld-servers.net | ||||||
| SOA | a.gtld-servers.netnstld@verisign-grs.com serial=1786264749 | ||||||
Same first word
codesanctuary.com |
DNS History
27 records (2 active, 25 former)
○NSns1.cloudns.net2015-05-04 → 2017-06-29 · 4 obs
● 2015-05-04 21:49:06
● 2017-06-29 04:52:00
○ 2026-03-29 17:00:28
○ 2026-08-09 08:55:50
● 2017-06-29 04:52:00
○ 2026-03-29 17:00:28
○ 2026-08-09 08:55:50
●NSns1.dns-expired.com2026-08-09 → 2026-08-09 · 3 obs
○ 2026-06-08 01:20:42
● 2026-08-09 01:42:28
● 2026-08-09 08:55:50
● 2026-08-09 01:42:28
● 2026-08-09 08:55:50
○NSns1.dns-parking.com2026-03-29 → 2026-06-08 · 5 obs
○ 2017-06-29 04:52:00
● 2026-03-29 17:00:28
● 2026-06-08 01:20:42
○ 2026-08-09 01:42:28
○ 2026-08-09 08:55:50
● 2026-03-29 17:00:28
● 2026-06-08 01:20:42
○ 2026-08-09 01:42:28
○ 2026-08-09 08:55:50
○NSns2.cloudns.net2015-05-04 → 2017-06-29 · 4 obs
● 2015-05-04 21:49:06
● 2017-06-29 04:52:00
○ 2026-03-29 17:00:28
○ 2026-08-09 08:55:50
● 2017-06-29 04:52:00
○ 2026-03-29 17:00:28
○ 2026-08-09 08:55:50
●NSns2.dns-expired.com2026-08-09 → 2026-08-09 · 3 obs
○ 2026-06-08 01:20:42
● 2026-08-09 01:42:28
● 2026-08-09 08:55:50
● 2026-08-09 01:42:28
● 2026-08-09 08:55:50
○NSns2.dns-parking.com2026-03-29 → 2026-06-08 · 5 obs
○ 2017-06-29 04:52:00
● 2026-03-29 17:00:28
● 2026-06-08 01:20:42
○ 2026-08-09 01:42:28
○ 2026-08-09 08:55:50
● 2026-03-29 17:00:28
● 2026-06-08 01:20:42
○ 2026-08-09 01:42:28
○ 2026-08-09 08:55:50
○NSns3.cloudns.net2015-05-04 → 2017-06-29 · 4 obs
● 2015-05-04 21:49:06
● 2017-06-29 04:52:00
○ 2026-03-29 17:00:28
○ 2026-08-09 08:55:50
● 2017-06-29 04:52:00
○ 2026-03-29 17:00:28
○ 2026-08-09 08:55:50
○NSns4.cloudns.net2015-05-04 → 2017-06-29 · 4 obs
● 2015-05-04 21:49:06
● 2017-06-29 04:52:00
○ 2026-03-29 17:00:28
○ 2026-08-09 08:55:50
● 2017-06-29 04:52:00
○ 2026-03-29 17:00:28
○ 2026-08-09 08:55:50
○NSpns1.cloudns.net2015-05-04 → 2017-06-29 · 4 obs
● 2015-05-04 21:49:06
● 2017-06-29 04:52:00
○ 2026-03-29 17:00:28
○ 2026-08-09 08:55:50
● 2017-06-29 04:52:00
○ 2026-03-29 17:00:28
○ 2026-08-09 08:55:50
○NSpns2.cloudns.net2015-05-04 → 2017-06-29 · 4 obs
● 2015-05-04 21:49:06
● 2017-06-29 04:52:00
○ 2026-03-29 17:00:28
○ 2026-08-09 08:55:50
● 2017-06-29 04:52:00
○ 2026-03-29 17:00:28
○ 2026-08-09 08:55:50
○NSpns3.cloudns.net2015-05-04 → 2017-06-29 · 4 obs
● 2015-05-04 21:49:06
● 2017-06-29 04:52:00
○ 2026-03-29 17:00:28
○ 2026-08-09 08:55:50
● 2017-06-29 04:52:00
○ 2026-03-29 17:00:28
○ 2026-08-09 08:55:50
○NSpns4.cloudns.net2015-05-04 → 2017-06-29 · 4 obs
● 2015-05-04 21:49:06
● 2017-06-29 04:52:00
○ 2026-03-29 17:00:28
○ 2026-08-09 08:55:50
● 2017-06-29 04:52:00
○ 2026-03-29 17:00:28
○ 2026-08-09 08:55:50
○NSpns5.cloudns.net2015-05-04 → 2017-06-29 · 4 obs
● 2015-05-04 21:49:06
● 2017-06-29 04:52:00
○ 2026-03-29 17:00:28
○ 2026-08-09 08:55:50
● 2017-06-29 04:52:00
○ 2026-03-29 17:00:28
○ 2026-08-09 08:55:50
○NSpns6.cloudns.net2015-05-04 → 2017-06-29 · 4 obs
● 2015-05-04 21:49:06
● 2017-06-29 04:52:00
○ 2026-03-29 17:00:28
○ 2026-08-09 08:55:50
● 2017-06-29 04:52:00
○ 2026-03-29 17:00:28
○ 2026-08-09 08:55:50
○NSpns7.cloudns.net2015-05-04 → 2017-06-29 · 4 obs
● 2015-05-04 21:49:06
● 2017-06-29 04:52:00
○ 2026-03-29 17:00:28
○ 2026-08-09 08:55:50
● 2017-06-29 04:52:00
○ 2026-03-29 17:00:28
○ 2026-08-09 08:55:50
○NSpns8.cloudns.net2015-05-04 → 2017-06-29 · 4 obs
● 2015-05-04 21:49:06
● 2017-06-29 04:52:00
○ 2026-03-29 17:00:28
○ 2026-08-09 08:55:50
● 2017-06-29 04:52:00
○ 2026-03-29 17:00:28
○ 2026-08-09 08:55:50
○NSpns9.cloudns.net2015-05-04 → 2017-06-29 · 4 obs
● 2015-05-04 21:49:06
● 2017-06-29 04:52:00
○ 2026-03-29 17:00:28
○ 2026-08-09 08:55:50
● 2017-06-29 04:52:00
○ 2026-03-29 17:00:28
○ 2026-08-09 08:55:50
○MXalt1.aspmx.l.google.com2015-05-04 → 2017-06-29 · 4 obs
● 2015-05-04 21:49:06
● 2017-06-29 04:52:00
○ 2026-03-29 17:00:28
○ 2026-08-09 08:55:50
● 2017-06-29 04:52:00
○ 2026-03-29 17:00:28
○ 2026-08-09 08:55:50
○MXalt2.aspmx.l.google.com2015-05-04 → 2017-06-29 · 4 obs
● 2015-05-04 21:49:06
● 2017-06-29 04:52:00
○ 2026-03-29 17:00:28
○ 2026-08-09 08:55:50
● 2017-06-29 04:52:00
○ 2026-03-29 17:00:28
○ 2026-08-09 08:55:50
○MXaspmx.l.google.com2015-05-04 → 2017-06-29 · 4 obs
● 2015-05-04 21:49:06
● 2017-06-29 04:52:00
○ 2026-03-29 17:00:28
○ 2026-08-09 08:55:50
● 2017-06-29 04:52:00
○ 2026-03-29 17:00:28
○ 2026-08-09 08:55:50
○MXaspmx2.googlemail.com2015-05-04 → 2017-06-29 · 4 obs
● 2015-05-04 21:49:06
● 2017-06-29 04:52:00
○ 2026-03-29 17:00:28
○ 2026-08-09 08:55:50
● 2017-06-29 04:52:00
○ 2026-03-29 17:00:28
○ 2026-08-09 08:55:50
○MXaspmx3.googlemail.com2015-05-04 → 2017-06-29 · 4 obs
● 2015-05-04 21:49:06
● 2017-06-29 04:52:00
○ 2026-03-29 17:00:28
○ 2026-08-09 08:55:50
● 2017-06-29 04:52:00
○ 2026-03-29 17:00:28
○ 2026-08-09 08:55:50
○MXmx1.hostinger.com2026-03-29 → 2026-06-08 · 5 obs
○ 2017-06-29 04:52:00
● 2026-03-29 17:00:28
● 2026-06-08 01:20:42
○ 2026-08-09 01:42:28
○ 2026-08-09 08:55:50
● 2026-03-29 17:00:28
● 2026-06-08 01:20:42
○ 2026-08-09 01:42:28
○ 2026-08-09 08:55:50
○MXmx2.hostinger.com2026-03-29 → 2026-06-08 · 5 obs
○ 2017-06-29 04:52:00
● 2026-03-29 17:00:28
● 2026-06-08 01:20:42
○ 2026-08-09 01:42:28
○ 2026-08-09 08:55:50
● 2026-03-29 17:00:28
● 2026-06-08 01:20:42
○ 2026-08-09 01:42:28
○ 2026-08-09 08:55:50
○A157.173.208.1002026-03-29 → 2026-06-08 · 5 obs
○ 2017-06-29 04:52:00
● 2026-03-29 17:00:28
● 2026-06-08 01:20:42
○ 2026-08-09 01:42:28
○ 2026-08-09 08:55:50
● 2026-03-29 17:00:28
● 2026-06-08 01:20:42
○ 2026-08-09 01:42:28
○ 2026-08-09 08:55:50
○A2a02:4780:2b:1636:0:6d8:e080:52026-03-29 → 2026-06-08 · 5 obs
○ 2017-06-29 04:52:00
● 2026-03-29 17:00:28
● 2026-06-08 01:20:42
○ 2026-08-09 01:42:28
○ 2026-08-09 08:55:50
● 2026-03-29 17:00:28
● 2026-06-08 01:20:42
○ 2026-08-09 01:42:28
○ 2026-08-09 08:55:50
○A5.9.107.1142015-05-04 → 2017-06-29 · 4 obs
● 2015-05-04 21:49:06
● 2017-06-29 04:52:00
○ 2026-03-29 17:00:28
○ 2026-08-09 08:55:50
● 2017-06-29 04:52:00
○ 2026-03-29 17:00:28
○ 2026-08-09 08:55:50
🔍 DNS Trace
Analysis
Name Servers
codesanctuary.com has two authoritative name servers — ns1.dns-expired.com and ns2.dns-expired.com.
codesanctuary.com has the same name server delegation as a number of other domains, such as host-88-204-17-171.tomcity.net, seneannonces.com, 5movierulz.tech and two more.
Both ns1.dns-expired.com and ns2.dns-expired.com have two IP addresses each. ns1.dns-expired.com resolves to 217.65.148.99 and 2a02:4780:27:abcd::34; ns2.dns-expired.com resolves to 217.21.79.21 and 2a02:4780:b:abcd::d.