croncode.com - dns.ninja

croncode.com

DNSSEC⚠️ Not signed
NSdns12.ovh.net ⚠️ Not in zone NS records
A2001:41d0:d00:f100::2🇫🇷 OVH2001:41d0::/32 IPv6
PTRdns12.ovh.net
A5.135.86.81🇫🇷 OVH5.135.0.0/16
PTRdns12.ovh.net
NSns12.ovh.net ⚠️ Not in zone NS records
A2001:41d0:b00:eb00::2🇫🇷 OVH2001:41d0::/32 IPv6
PTRns12.ovh.net
A5.39.102.21🇫🇷 OVH5.39.0.0/17 ISP Paris, France
PTRns12.ovh.net

com

Same first word

Similar names

DNS History

13 records (2 active, 11 former)

20162017201820192020202120222023202420252026NSdns12.ovh.netns12.ovh.netns-1346.awsdns-40.orgns-1593.awsdns-07.co.ukns-313.awsdns-39.comns-521.awsdns-01.netns09.domaincontrol.comns10.domaincontrol.comns57.domaincontrol.comns58.domaincontrol.comMXmailstore1.secureserver.netsmtp.secureserver.netA50.63.202.35
NSdns12.ovh.net2026-03-26 → 2026-06-28 · 3 obs
○ 2019-04-10 01:55:46
● 2026-03-26 13:19:28
● 2026-06-28 13:25:50
NSns-1346.awsdns-40.org2017-02-01 → 2017-02-01 · 4 obs
○ 2016-04-12 03:31:58
● 2017-02-01 20:52:10
○ 2019-04-10 01:55:46
○ 2026-06-28 13:25:50
NSns-1593.awsdns-07.co.uk2017-02-01 → 2017-02-01 · 4 obs
○ 2016-04-12 03:31:58
● 2017-02-01 20:52:10
○ 2019-04-10 01:55:46
○ 2026-06-28 13:25:50
NSns-313.awsdns-39.com2017-02-01 → 2017-02-01 · 4 obs
○ 2016-04-12 03:31:58
● 2017-02-01 20:52:10
○ 2019-04-10 01:55:46
○ 2026-06-28 13:25:50
NSns-521.awsdns-01.net2017-02-01 → 2017-02-01 · 4 obs
○ 2016-04-12 03:31:58
● 2017-02-01 20:52:10
○ 2019-04-10 01:55:46
○ 2026-06-28 13:25:50
NSns09.domaincontrol.com2016-01-15 → 2016-01-15 · 4 obs
○ 2015-10-29 01:49:00
● 2016-01-15 13:39:58
○ 2016-04-12 03:31:58
○ 2026-06-28 13:25:50
NSns10.domaincontrol.com2016-01-15 → 2016-01-15 · 4 obs
○ 2015-10-29 01:49:00
● 2016-01-15 13:39:58
○ 2016-04-12 03:31:58
○ 2026-06-28 13:25:50
NSns12.ovh.net2026-03-26 → 2026-06-28 · 3 obs
○ 2019-04-10 01:55:46
● 2026-03-26 13:19:28
● 2026-06-28 13:25:50
NSns57.domaincontrol.com2015-06-10 → 2015-10-29 · 4 obs
● 2015-06-10 19:18:40
● 2015-10-29 01:49:00
○ 2016-01-15 13:39:58
○ 2026-06-28 13:25:50
NSns58.domaincontrol.com2015-06-10 → 2015-10-29 · 4 obs
● 2015-06-10 19:18:40
● 2015-10-29 01:49:00
○ 2016-01-15 13:39:58
○ 2026-06-28 13:25:50
MXmailstore1.secureserver.net2015-06-10 → 2016-01-15 · 4 obs
● 2015-06-10 19:18:40
● 2016-01-15 13:39:58
○ 2016-04-12 03:31:58
○ 2026-06-28 13:25:50
MXsmtp.secureserver.net2015-06-10 → 2016-01-15 · 4 obs
● 2015-06-10 19:18:40
● 2016-01-15 13:39:58
○ 2016-04-12 03:31:58
○ 2026-06-28 13:25:50
A50.63.202.352015-06-10 → 2016-01-15 · 4 obs
● 2015-06-10 19:18:40
● 2016-01-15 13:39:58
○ 2016-04-12 03:31:58
○ 2026-06-28 13:25:50

🔍 DNS Trace

📋 Delegation Chain

ZoneNameserversGlue
comm.gtld-servers.net, f.gtld-servers.net, b.gtld-servers.net, k.gtld-servers.net...-
croncode.comdns12.ovh.net, ns12.ovh.net-

✅ Authoritative Response

Server:5.39.102.21

NS records: dns12.ovh.net, ns12.ovh.net

🔒 DNSSEC Status

❌ Bogus (DNSSEC validation failed)

No DNSKEY for croncode.com

⏱️ Timing

Total: 784ms | Queries: -

📄 Records

TypeCountSample Data

Analysis

Name Servers

croncode.com has two authoritative name servers — dns12.ovh.net and ns12.ovh.net.

croncode.com has the same name server delegation as a number of other domains, such as rivedigital.com, esvp.fr, peugeot-daxauto.fr and two more.

croncode.com has a partial name server overlap with other domains — among them frostpol.com and ceremh.org.

Both dns12.ovh.net and ns12.ovh.net have two IP addresses each. dns12.ovh.net resolves to 5.135.86.81 and 2001:41d0:d00:f100::2; ns12.ovh.net resolves to 5.39.102.21 and 2001:41d0:b00:eb00::2.