codingape.com - dns.ninja
codingape.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@codingape.com 2025-12-16 #4 | ||||||
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=1787824925 | ||||||
Same first word
codingape.com |
Similar names
Previous names
Next names
DNS History
8 records (3 active, 5 former)
●NSns1.atom.com2026-08-18 → 2026-08-27 · 3 obs
○ 2016-09-17 00:17:36
● 2026-08-18 09:38:58
● 2026-08-27 10:10:14
● 2026-08-18 09:38:58
● 2026-08-27 10:10:14
●NSns2.atom.com2026-08-18 → 2026-08-27 · 3 obs
○ 2016-09-17 00:17:36
● 2026-08-18 09:38:58
● 2026-08-27 10:10:14
● 2026-08-18 09:38:58
● 2026-08-27 10:10:14
○NSxp1.namesbeyond.com2015-06-25 → 2016-09-17 · 4 obs
● 2015-06-25 20:53:38
● 2016-09-17 00:17:36
○ 2026-08-18 09:38:58
○ 2026-08-27 10:10:14
● 2016-09-17 00:17:36
○ 2026-08-18 09:38:58
○ 2026-08-27 10:10:14
○NSxp2.namesbeyond.com2015-06-25 → 2016-09-17 · 4 obs
● 2015-06-25 20:53:38
● 2016-09-17 00:17:36
○ 2026-08-18 09:38:58
○ 2026-08-27 10:10:14
● 2016-09-17 00:17:36
○ 2026-08-18 09:38:58
○ 2026-08-27 10:10:14
○A208.91.197.1152015-06-25 → 2016-03-29 · 7 obs
● 2015-06-25 20:53:38
● 2015-11-03 08:46:04
○ 2016-02-24 01:47:42
○ 2016-03-14 17:10:52
● 2016-03-29 15:09:20
○ 2016-09-17 00:17:36
○ 2026-08-27 10:10:14
● 2015-11-03 08:46:04
○ 2016-02-24 01:47:42
○ 2016-03-14 17:10:52
● 2016-03-29 15:09:20
○ 2016-09-17 00:17:36
○ 2026-08-27 10:10:14
○A209.160.74.1512015-06-25 → 2015-06-25 · 3 obs
● 2015-06-25 20:53:38
○ 2026-08-18 09:38:58
○ 2026-08-27 10:10:14
○ 2026-08-18 09:38:58
○ 2026-08-27 10:10:14
●A52.20.84.622026-08-18 → 2026-08-27 · 3 obs
○ 2016-09-17 00:17:36
● 2026-08-18 09:38:58
● 2026-08-27 10:10:14
● 2026-08-18 09:38:58
● 2026-08-27 10:10:14
○A74.84.144.322016-02-24 → 2016-09-17 · 7 obs
○ 2015-11-03 08:46:04
● 2016-02-24 01:47:42
● 2016-03-14 17:10:52
○ 2016-03-29 15:09:20
● 2016-09-17 00:17:36
○ 2026-08-18 09:38:58
○ 2026-08-27 10:10:14
● 2016-02-24 01:47:42
● 2016-03-14 17:10:52
○ 2016-03-29 15:09:20
● 2016-09-17 00:17:36
○ 2026-08-18 09:38:58
○ 2026-08-27 10:10:14
🔍 DNS Trace
Analysis
IP Addresses
codingape.com has exactly one IP address — 52.20.84.62.
fanhook.com, introdirect.com, watchmaster.co.uk plus two other host names have IP numbers in common with codingape.com.
Name Servers
Two name servers handle the delegation for codingape.com: ns1.atom.com and ns2.atom.com.
The name server configuration of codingape.com is shared with other domains, for instance company.beer, groominggirl.com, patientive.com and two others.
codingape.com has at least partial name server overlap with other domains, such as miraoptics.com, relationshipcounselling.in, paypay.us and two others.
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.