climbforce.com - dns.ninja
climbforce.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 | ||||||
| TXT | f0095018235b8109a2bf9f65674a1784b6971ed6 | ||||||
| SOA | ns1.atom.comhostmaster@climbforce.com 2025-11-04 #1 | ||||||
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=1786906089 | ||||||
Same first word
climbforce.com |
DNS History
18 records (3 active, 15 former)
○NSdns1.registrar-servers.com2015-07-22 → 2020-01-09 · 4 obs
● 2015-07-22 12:36:12
● 2020-01-09 14:20:06
○ 2026-02-20 08:07:12
○ 2026-08-16 19:13:54
● 2020-01-09 14:20:06
○ 2026-02-20 08:07:12
○ 2026-08-16 19:13:54
○NSdns2.registrar-servers.com2015-07-22 → 2020-01-09 · 4 obs
● 2015-07-22 12:36:12
● 2020-01-09 14:20:06
○ 2026-02-20 08:07:12
○ 2026-08-16 19:13:54
● 2020-01-09 14:20:06
○ 2026-02-20 08:07:12
○ 2026-08-16 19:13:54
○NSdns3.registrar-servers.com2015-07-22 → 2017-02-14 · 4 obs
● 2015-07-22 12:36:12
● 2017-02-14 20:06:30
○ 2020-01-09 14:20:06
○ 2026-08-16 19:13:54
● 2017-02-14 20:06:30
○ 2020-01-09 14:20:06
○ 2026-08-16 19:13:54
○NSdns4.registrar-servers.com2015-07-22 → 2017-02-14 · 4 obs
● 2015-07-22 12:36:12
● 2017-02-14 20:06:30
○ 2020-01-09 14:20:06
○ 2026-08-16 19:13:54
● 2017-02-14 20:06:30
○ 2020-01-09 14:20:06
○ 2026-08-16 19:13:54
○NSdns5.registrar-servers.com2015-07-22 → 2017-02-14 · 4 obs
● 2015-07-22 12:36:12
● 2017-02-14 20:06:30
○ 2020-01-09 14:20:06
○ 2026-08-16 19:13:54
● 2017-02-14 20:06:30
○ 2020-01-09 14:20:06
○ 2026-08-16 19:13:54
●NSns1.atom.com2026-02-20 → 2026-08-16 · 3 obs
○ 2020-01-09 14:20:06
● 2026-02-20 08:07:12
● 2026-08-16 19:13:54
● 2026-02-20 08:07:12
● 2026-08-16 19:13:54
●NSns2.atom.com2026-02-20 → 2026-08-16 · 3 obs
○ 2020-01-09 14:20:06
● 2026-02-20 08:07:12
● 2026-08-16 19:13:54
● 2026-02-20 08:07:12
● 2026-08-16 19:13:54
○MXalt1.aspmx.l.google.com2015-07-22 → 2020-01-09 · 4 obs
● 2015-07-22 12:36:12
● 2020-01-09 14:20:06
○ 2026-02-20 08:07:12
○ 2026-08-16 19:13:54
● 2020-01-09 14:20:06
○ 2026-02-20 08:07:12
○ 2026-08-16 19:13:54
○MXalt2.aspmx.l.google.com2015-07-22 → 2020-01-09 · 4 obs
● 2015-07-22 12:36:12
● 2020-01-09 14:20:06
○ 2026-02-20 08:07:12
○ 2026-08-16 19:13:54
● 2020-01-09 14:20:06
○ 2026-02-20 08:07:12
○ 2026-08-16 19:13:54
○MXaspmx.l.google.com2015-07-22 → 2020-01-09 · 4 obs
● 2015-07-22 12:36:12
● 2020-01-09 14:20:06
○ 2026-02-20 08:07:12
○ 2026-08-16 19:13:54
● 2020-01-09 14:20:06
○ 2026-02-20 08:07:12
○ 2026-08-16 19:13:54
○MXaspmx2.googlemail.com2015-07-22 → 2020-01-09 · 4 obs
● 2015-07-22 12:36:12
● 2020-01-09 14:20:06
○ 2026-02-20 08:07:12
○ 2026-08-16 19:13:54
● 2020-01-09 14:20:06
○ 2026-02-20 08:07:12
○ 2026-08-16 19:13:54
○MXaspmx3.googlemail.com2015-07-22 → 2020-01-09 · 4 obs
● 2015-07-22 12:36:12
● 2020-01-09 14:20:06
○ 2026-02-20 08:07:12
○ 2026-08-16 19:13:54
● 2020-01-09 14:20:06
○ 2026-02-20 08:07:12
○ 2026-08-16 19:13:54
○MXaspmx4.googlemail.com2015-07-22 → 2020-01-09 · 4 obs
● 2015-07-22 12:36:12
● 2020-01-09 14:20:06
○ 2026-02-20 08:07:12
○ 2026-08-16 19:13:54
● 2020-01-09 14:20:06
○ 2026-02-20 08:07:12
○ 2026-08-16 19:13:54
○MXaspmx5.googlemail.com2015-07-22 → 2020-01-09 · 4 obs
● 2015-07-22 12:36:12
● 2020-01-09 14:20:06
○ 2026-02-20 08:07:12
○ 2026-08-16 19:13:54
● 2020-01-09 14:20:06
○ 2026-02-20 08:07:12
○ 2026-08-16 19:13:54
○A130.211.63.1912016-02-12 → 2017-02-14 · 5 obs
○ 2015-11-23 10:07:22
● 2016-02-12 19:01:10
● 2017-02-14 20:06:30
○ 2020-01-09 14:20:06
○ 2026-08-16 19:13:54
● 2016-02-12 19:01:10
● 2017-02-14 20:06:30
○ 2020-01-09 14:20:06
○ 2026-08-16 19:13:54
○A46.101.167.2522020-01-09 → 2020-01-09 · 4 obs
○ 2017-02-14 20:06:30
● 2020-01-09 14:20:06
○ 2026-02-20 08:07:12
○ 2026-08-16 19:13:54
● 2020-01-09 14:20:06
○ 2026-02-20 08:07:12
○ 2026-08-16 19:13:54
●A52.20.84.622026-02-20 → 2026-08-16 · 3 obs
○ 2020-01-09 14:20:06
● 2026-02-20 08:07:12
● 2026-08-16 19:13:54
● 2026-02-20 08:07:12
● 2026-08-16 19:13:54
○A68.65.123.2092015-07-22 → 2015-11-23 · 4 obs
● 2015-07-22 12:36:12
● 2015-11-23 10:07:22
○ 2016-02-12 19:01:10
○ 2026-08-16 19:13:54
● 2015-11-23 10:07:22
○ 2016-02-12 19:01:10
○ 2026-08-16 19:13:54
🔍 DNS Trace
Analysis
IP Addresses
climbforce.com resolves to just one IP address, 52.20.84.62.
Two other host names, along with www.(0x706f726e)omax.com, www.daytonafunmachines.com and fursu.com, also share IP numbers with climbforce.com.
Name Servers
The NS records for climbforce.com delegate to ns1.atom.com and ns2.atom.com.
climbforce.com shares its NS records with other domains, for example eznews.com, amako.com, rampsoft.com and two others.
There is at least partial name server overlap between climbforce.com and other domains — sulki.com, muhawala.com, firexe.com and two more among them.
These name servers are routinely deployed together with the name servers verification-sma9ty5qx4h9thyd6tt6vt.ns101.verify.hn.
ns1.atom.com → 44.219.81.145 and ns2.atom.com → 50.19.240.86: one IP number per host name.