milicode.com - dns.ninja
milicode.com
| DNSSEC | ⚠️ Not signed | ||||||
| A | 52.20.84.62🇺🇸 Amazon52.20.0.0/14 EC2 IAD prefix | ||||||
| PTR | ec2-52-20-84-62.compute-1.amazonaws.com | ||||||
| NS | ns1.atom.com ⭐ | ||||||
| A | 44.219.81.145🇺🇸 Amazon44.192.0.0/11 EC2 IAD prefix | ||||||
| PTR | ec2-44-219-81-145.compute-1.amazonaws.com | ||||||
| NS | ns2.atom.com | ||||||
| A | 50.19.240.86🇺🇸 Amazon50.19.128.0/17 EC2 IAD prefix | ||||||
| PTR | ec2-50-19-240-86.compute-1.amazonaws.com | ||||||
| SOA | ns1.atom.comhostmaster@milicode.com 2025-11-25 #6 | ||||||
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=1783867912 | ||||||
Same first word
milicode.com |
Similar names
DNS History
9 records (3 active, 6 former)
○NSdns.ovh.net2015-08-04 → 2018-06-26 · 4 obs
● 2018-06-26 10:03:58
○ 2026-04-01 00:51:40
○ 2026-07-12 15:14:46
○NSns.ovh.net2015-08-04 → 2018-06-26 · 4 obs
● 2018-06-26 10:03:58
○ 2026-04-01 00:51:40
○ 2026-07-12 15:14:46
●NSns1.atom.com2026-04-01 → 2026-07-12 · 3 obs
● 2026-04-01 00:51:40
● 2026-07-12 15:14:46
●NSns2.atom.com2026-04-01 → 2026-07-12 · 3 obs
● 2026-04-01 00:51:40
● 2026-07-12 15:14:46
○MXmx1.ovh.net2015-08-04 → 2018-06-26 · 4 obs
● 2018-06-26 10:03:58
○ 2026-04-01 00:51:40
○ 2026-07-12 15:14:46
○MXmx2.ovh.net2015-08-04 → 2018-06-26 · 4 obs
● 2018-06-26 10:03:58
○ 2026-04-01 00:51:40
○ 2026-07-12 15:14:46
○A118.128.66.1512015-08-04 → 2015-08-04 · 3 obs
○ 2017-02-06 09:29:24
○ 2026-07-12 15:14:46
○A213.186.33.22015-08-04 → 2018-06-26 · 4 obs
● 2018-06-26 10:03:58
○ 2026-04-01 00:51:40
○ 2026-07-12 15:14:46
●A52.20.84.622026-04-01 → 2026-07-12 · 3 obs
● 2026-04-01 00:51:40
● 2026-07-12 15:14:46
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | c.gtld-servers.net, d.gtld-servers.net, f.gtld-servers.net, g.gtld-servers.net... | - |
| milicode.com | ns1.atom.com, ns2.atom.com | 2 records |
✅ Authoritative Response
Server:44.219.81.145
NS records: ns1.atom.com, ns2.atom.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for milicode.com (unsigned zone)
⏱️ Timing
Total: 3504ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 52.20.84.62 |
| NS | 2 | ns2.atom.com, ns1.atom.com |
| SOA | 1 | ns1.atom.com hostmaster.milicode.com |
📌 Glue Records Collected
Total: 2
Out-of-bailiwick: 2 (ns1.atom.com, ns2.atom.com)
Analysis
IP Addresses
milicode.com resolves to just one IP address, 52.20.84.62.
Two other host names, along with notecall.com, imez.com and www.swc.ae, also share IP numbers with milicode.com.
Name Servers
milicode.com is served by two delegated name servers, ns1.atom.com and ns2.atom.com.
milicode.com shares its NS records with other domains, for example coogame.com, kirbe.com, vevala.com and two others.
The DNS delegation for milicode.com at least partly coincides with that of other domains, botvi.com being one example.
ns1.atom.com directs to 44.219.81.145 and ns2.atom.com directs to 50.19.240.86; each host name points to exactly one IP number.