curesignal.com - robtex.com
curesignal.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 ⭐ ⚠️ Not in zone NS records | ||||||
| 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 ⚠️ Not in zone NS records | ||||||
| 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@curesignal.com 2025-11-03 #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=1776148612 | ||||||
Same first word
curesignal.com |
Similar names
surgilance.com |
nesurgical.com |
ergunsalci.com |
nucleargis.com |
surgilance.at |
usclearing.com |
nesurgical.org |
securilang.com |
signalcure.com |
crueligans.com |
DNS History
12 records (3 active, 9 former)
○NSeric.ns.cloudflare.com2019-01-28 → 2019-01-28 · 4 obs
● 2019-01-28 21:02:16
○ 2026-03-25 11:29:18
○ 2026-04-14 06:44:42
○NSlila.ns.cloudflare.com2019-01-28 → 2019-01-28 · 4 obs
● 2019-01-28 21:02:16
○ 2026-03-25 11:29:18
○ 2026-04-14 06:44:42
●NSns1.atom.com2026-03-25 → 2026-04-14 · 3 obs
● 2026-03-25 11:29:18
● 2026-04-14 06:44:42
○NSns1.bodis.com2016-12-18 → 2016-12-18 · 3 obs
○ 2019-01-28 21:02:16
○ 2026-04-14 06:44:42
●NSns2.atom.com2026-03-25 → 2026-04-14 · 3 obs
● 2026-03-25 11:29:18
● 2026-04-14 06:44:42
○NSns2.bodis.com2016-12-18 → 2016-12-18 · 3 obs
○ 2019-01-28 21:02:16
○ 2026-04-14 06:44:42
○A104.28.28.1082019-01-28 → 2019-01-28 · 4 obs
● 2019-01-28 21:02:16
○ 2026-03-25 11:29:18
○ 2026-04-14 06:44:42
○A104.28.29.1082019-01-28 → 2019-01-28 · 4 obs
● 2019-01-28 21:02:16
○ 2026-03-25 11:29:18
○ 2026-04-14 06:44:42
○A199.59.243.1202016-12-18 → 2016-12-18 · 3 obs
○ 2019-01-28 21:02:16
○ 2026-04-14 06:44:42
○A2606:4700:30::681c:1c6c2019-01-28 → 2019-01-28 · 4 obs
● 2019-01-28 21:02:16
○ 2026-03-25 11:29:18
○ 2026-04-14 06:44:42
○A2606:4700:30::681c:1d6c2019-01-28 → 2019-01-28 · 4 obs
● 2019-01-28 21:02:16
○ 2026-03-25 11:29:18
○ 2026-04-14 06:44:42
●A52.20.84.622026-03-25 → 2026-04-14 · 3 obs
● 2026-03-25 11:29:18
● 2026-04-14 06:44:42
🔍 DNS Trace
Analysis
IP Addresses
curesignal.com resolves to one IP number: 52.20.84.62.
Other host names, for instance ztarget.com, futuredent.com, payshoot.com, pichef.com and fileavenue.com share IP numbers with curesignal.com.
Name Servers
curesignal.com's delegation uses two name servers: ns1.atom.com and ns2.atom.com.
curesignal.com uses the same name server setup as other domains, such as wahebi.com, 690.us, noirhomes.com, cgsl.com and urbangents.com.
curesignal.com at least partially shares name servers with other domains, including lcmv.com, holom.net, mrforge.com, sor.me and flyprix.com.
These name servers are commonly used with verification-yhehuhyrvixzqbtydgzisf.ns101.verify.hn.
Host names with a single IP address: ns1.atom.com points to 44.219.81.145; ns2.atom.com points to 50.19.240.86.