klimsa.com - dns.ninja
klimsa.com
| DNSSEC | ⚠️ Not signed | ||||||
| A | 66.45.246.141🇺🇸 NJIIX-166.45.224.0/19 NJIIX.net 110B Meadowlands Pkwy Secaucus, NJ 07094 | ||||||
| NS | ns1.domainrecover.com ⭐ | ||||||
| A | 149.248.38.58🇺🇸 AS-VULTR149.248.32.0/20 Vultr Assigned Prefix | ||||||
| PTR | 149.248.38.58.vultrusercontent.com | ||||||
| NS | ns2.domainrecover.com | ||||||
| A | 199.247.16.62🇩🇪 AS-VULTR199.247.16.0/21 Vultr Assigned Prefix | ||||||
| PTR | 199.247.16.62.vultrusercontent.com | ||||||
| TXT | yGjyZf7SHD | ||||||
| SOA | ns1.domainrecover.comhostmaster@domainreover.com serial=1623031840 | ||||||
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=1786736769 | ||||||
Same first word
Similar names
DNS History
11 records (3 active, 8 former)
●NSns1.domainrecover.com2026-03-05 → 2026-08-14 · 3 obs
● 2026-03-05 02:34:22
● 2026-08-14 20:13:44
○NSns1.dsredirection.com2016-06-21 → 2016-06-21 · 3 obs
○ 2017-04-04 10:09:52
○ 2026-08-14 20:13:44
●NSns2.domainrecover.com2026-03-05 → 2026-08-14 · 3 obs
● 2026-03-05 02:34:22
● 2026-08-14 20:13:44
○NSns2.dsredirection.com2016-06-21 → 2016-06-21 · 3 obs
○ 2017-04-04 10:09:52
○ 2026-08-14 20:13:44
○MXmxs1.fides.com2015-07-13 → 2016-03-03 · 4 obs
● 2016-03-03 04:30:08
○ 2016-06-21 22:14:06
○ 2026-08-14 20:13:44
○MXmxs2.fides.com2015-07-13 → 2016-03-03 · 4 obs
● 2016-03-03 04:30:08
○ 2016-06-21 22:14:06
○ 2026-08-14 20:13:44
○A141.8.230.202016-06-21 → 2017-04-04 · 5 obs
● 2016-06-21 22:14:06
● 2017-04-04 10:09:52
○ 2026-03-05 02:34:22
○ 2026-08-14 20:13:44
○A64.20.39.1342015-07-13 → 2016-03-03 · 4 obs
● 2016-03-03 04:30:08
○ 2016-06-21 22:14:06
○ 2026-08-14 20:13:44
●A66.45.246.1412026-03-05 → 2026-08-14 · 3 obs
● 2026-03-05 02:34:22
● 2026-08-14 20:13:44
○CNAMEpres.serverhome.com2016-06-21 → 2017-04-04 · 4 obs
● 2017-04-04 10:09:52
○ 2026-03-05 02:34:22
○ 2026-08-14 20:13:44
○CNAMEthie5ku9.dsgeneration.com2016-06-21 → 2016-06-21 · 3 obs
○ 2017-04-04 10:09:52
○ 2026-08-14 20:13:44
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | h.gtld-servers.net, j.gtld-servers.net, l.gtld-servers.net, c.gtld-servers.net... | - |
| klimsa.com | ns1.domainrecover.com, ns2.domainrecover.com | 2 records |
✅ Authoritative Response
Server:199.247.16.62
NS records: ns1.domainrecover.com, ns2.domainrecover.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for klimsa.com (unsigned zone)
⏱️ Timing
Total: 1389ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 66.45.246.141 |
| NS | 2 | NS1.DOMAINRECOVER.com, NS2.DOMAINRECOVER.com |
| TXT | 1 | yGjyZf7SHD |
| SOA | 1 | ns1.domainrecover.com hostmaster.domainr |
📌 Glue Records Collected
Total: 2
Out-of-bailiwick: 2 (ns1.domainrecover.com, ns2.domainrecover.com)
Analysis
IP Addresses
klimsa.com resolves to just one IP address, 66.45.246.141.
Two other host names, along with active-access.com, klage.com and hakarz.com, also share IP numbers with klimsa.com.
Name Servers
klimsa.com has two authoritative name servers — ns1.domainrecover.com and ns2.domainrecover.com.
klimsa.com shares its NS records with other domains, for example valipour.com, angerson.com, grafomedia.com and two others.
The name servers of klimsa.com overlap at least partially with those of other domains — among them ktnnel.com, naused.com, falba.com and two more.
The name servers ns1.serverhome.com, ns2.serverhome.com and ns.europeanserver.com are commonly seen alongside these name servers.
Both ns1.domainrecover.com and ns2.domainrecover.com have a single IP address each — ns1.domainrecover.com resolves to 149.248.38.58 while ns2.domainrecover.com resolves to 199.247.16.62.