codefrenetics.com - dns.ninja
codefrenetics.com
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=1786456069 | ||||||
Same first word
codefrenetics.com |
DNS History
18 records (8 active, 10 former)
○NSns61.domaincontrol.com2018-08-31 → 2018-08-31 · 3 obs
○ 2026-02-25 15:30:02
○ 2026-08-11 13:57:34
○NSns62.domaincontrol.com2018-08-31 → 2018-08-31 · 3 obs
○ 2026-02-25 15:30:02
○ 2026-08-11 13:57:34
●NSns65.domaincontrol.com2026-02-25 → 2026-08-11 · 3 obs
● 2026-02-25 15:30:02
● 2026-08-11 13:57:34
●NSns66.domaincontrol.com2026-02-25 → 2026-08-11 · 3 obs
● 2026-02-25 15:30:02
● 2026-08-11 13:57:34
●MXalt1.aspmx.l.google.com2026-02-25 → 2026-08-11 · 2 obs
● 2026-08-11 13:57:34
●MXalt2.aspmx.l.google.com2026-02-25 → 2026-08-11 · 2 obs
● 2026-08-11 13:57:34
●MXalt3.aspmx.l.google.com2026-02-25 → 2026-08-11 · 2 obs
● 2026-08-11 13:57:34
●MXalt4.aspmx.l.google.com2026-02-25 → 2026-08-11 · 2 obs
● 2026-08-11 13:57:34
●MXaspmx.l.google.com2026-02-25 → 2026-08-11 · 2 obs
● 2026-08-11 13:57:34
○A184.168.221.322018-08-31 → 2018-08-31 · 3 obs
○ 2026-02-25 15:30:02
○ 2026-08-11 13:57:34
○A184.168.221.452018-08-31 → 2018-08-31 · 3 obs
○ 2026-02-25 15:30:02
○ 2026-08-11 13:57:34
●A5.189.144.1852026-02-25 → 2026-08-11 · 3 obs
● 2026-02-25 15:30:02
● 2026-08-11 13:57:34
○A50.63.202.412018-08-31 → 2018-08-31 · 3 obs
○ 2026-02-25 15:30:02
○ 2026-08-11 13:57:34
○A50.63.202.472018-08-31 → 2018-08-31 · 3 obs
○ 2026-02-25 15:30:02
○ 2026-08-11 13:57:34
○A50.63.202.512018-08-31 → 2018-08-31 · 3 obs
○ 2026-02-25 15:30:02
○ 2026-08-11 13:57:34
○A50.63.202.532018-08-31 → 2018-08-31 · 3 obs
○ 2026-02-25 15:30:02
○ 2026-08-11 13:57:34
○A50.63.202.562018-08-31 → 2018-08-31 · 3 obs
○ 2026-02-25 15:30:02
○ 2026-08-11 13:57:34
○A50.63.202.602018-08-31 → 2018-08-31 · 3 obs
○ 2026-02-25 15:30:02
○ 2026-08-11 13:57:34
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net... | - |
| codefrenetics.com | ns66.domaincontrol.com, ns65.domaincontrol.com | 4 records |
✅ Authoritative Response
Server:173.201.70.43
NS records: ns66.domaincontrol.com, ns65.domaincontrol.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for codefrenetics.com (unsigned zone)
⏱️ Timing
Total: 218ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 5.189.144.185 |
| NS | 2 | ns65.domaincontrol.com, ns66.domaincontrol.com |
| MX | 5 | aspmx.l.google.com (pri: 1), alt1.aspmx.l.google.com (pri: 5)... |
| TXT | 2 | v=spf1 include:_spf.google.com ~all, google-site-verification=dCdBe5MN40UPlms |
| SOA | 1 | ns65.domaincontrol.com dns.jomax.net |
📌 Glue Records Collected
Total: 4
Out-of-bailiwick: 4 (ns66.domaincontrol.com, ns66.domaincontrol.com, ns65.domaincontrol.com...)
Analysis
IP Addresses
codefrenetics.com directs to one IP number, which is 5.189.144.185.
Name Servers
codefrenetics.com has two authoritative name servers — ns65.domaincontrol.com and ns66.domaincontrol.com.
codefrenetics.com has the same name server delegation as a number of other domains, such as ccofcny.com, solessmanagement.com, mybarberisfresh.com and two more.
Both ns65.domaincontrol.com and ns66.domaincontrol.com have two IP addresses each. ns65.domaincontrol.com resolves to 97.74.102.43 and 2603:5:2164::2b; ns66.domaincontrol.com resolves to 173.201.70.43 and 2603:5:2264::2b.
Mail Servers
codefrenetics.com has five mail servers, which are aspmx.l.google.com, alt1.aspmx.l.google.com, alt2.aspmx.l.google.com and two others.
codefrenetics.com shares at least some of its mail servers with other domains — for example ns500699.ns500765.ns500765.ns500699.ns500699.ns500699.ns500734.ns500699.ns500699.ns500699.ns500588.ns500693.ns500699.ns500683.ns500683.ns500699.ns500612.ns500110.dtrkdll.com, ns500742.ns500754.ns500742.ns500731.ns500671.ns500671.ns500742.ns500704.ns500688.ns500291.ns500291.ns500666.tenderladiesbz.com, ns500759.ns500758.ns500758.ns500758.ns500758.ns500735.ns500698.ns500698.ns500736.ns500735.ns500708.ns500708.ns500708.ns500698.ns500576.ns500619.ns500619.trackreceptor.com and two more.
It is common to find these mail servers paired with mail servers alt3.aspmx.l.google.com, alt4.aspmx.l.google.com, aspmx2.googlemail.com and 3 more.
Hosts with two IP numbers each:
aspmx.l.google.com resolves to 64.233.180.27 and 2607:f8b0:4004:c1b::1a.
alt1.aspmx.l.google.com resolves to 192.178.234.27 and 2800:3f0:4003:c14::1a.
alt2.aspmx.l.google.com resolves to 172.253.116.26 and 2a00:1450:400b:c02::1b.
alt3.aspmx.l.google.com resolves to 192.178.223.26 and 2a00:1450:4009:c0f::1a.
alt4.aspmx.l.google.com resolves to 172.253.157.27 and 2a00:1450:400c:c23::1b.