currentcode.com - dns.ninja
currentcode.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@currentcode.com 2026-01-22 #3 | ||||||
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=1785557827 | ||||||
Same first word
currentcode.com |
Similar names
DNS History
10 records (3 active, 7 former)
○NSns1.adlistings.com2015-08-12 → 2018-08-19 · 4 obs
● 2018-08-19 02:48:14
○ 2026-02-26 16:29:06
○ 2026-08-01 04:24:08
●NSns1.atom.com2026-02-26 → 2026-08-01 · 3 obs
● 2026-02-26 16:29:06
● 2026-08-01 04:24:08
○NSns2.adlistings.com2015-08-12 → 2018-08-19 · 4 obs
● 2018-08-19 02:48:14
○ 2026-02-26 16:29:06
○ 2026-08-01 04:24:08
●NSns2.atom.com2026-02-26 → 2026-08-01 · 3 obs
● 2026-02-26 16:29:06
● 2026-08-01 04:24:08
○MXmail1.adlistings.com2015-08-12 → 2018-08-19 · 4 obs
● 2018-08-19 02:48:14
○ 2026-02-26 16:29:06
○ 2026-08-01 04:24:08
○A15.197.204.562026-02-26 → 2026-08-01 · 2 obs
○ 2026-08-01 04:24:08
○A206.214.168.342015-08-12 → 2018-08-19 · 4 obs
● 2018-08-19 02:48:14
○ 2026-02-26 16:29:06
○ 2026-08-01 04:24:08
●A52.20.84.622026-02-26 → 2026-08-01 · 6 obs
● 2026-02-26 16:29:06
● 2026-02-28 20:38:52
○ 2026-03-01 19:17:10
● 2026-03-01 20:49:02
● 2026-08-01 04:24:08
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net... | - |
| currentcode.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 currentcode.com (unsigned zone)
⏱️ Timing
Total: 3078ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 52.20.84.62 |
| NS | 2 | ns1.atom.com, ns2.atom.com |
| SOA | 1 | ns1.atom.com hostmaster.currentcode.com |
📌 Glue Records Collected
Total: 2
Out-of-bailiwick: 2 (ns1.atom.com, ns2.atom.com)
Analysis
IP Addresses
currentcode.com resolves to just one IP address, 52.20.84.62.
Two other host names, along with payleads.com, afacy.com and synlio.com, also share IP numbers with currentcode.com.
Name Servers
currentcode.com has two authoritative name servers — ns1.atom.com and ns2.atom.com.
currentcode.com shares its NS records with other domains, for example foxwa.com, fiplu.com, caremave.com and two others.
currentcode.com has at least partial name server overlap with other domains, such as tbpu.com, rateblend.com, migrz.com and two others.
It is common to find these name servers paired with the name servers verification-788sfmkgkaqbejp9kdtxlg.ns101.verify.hn.
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.