tidesensor.com - dns.ninja
tidesensor.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 | c356c182-fb79-4ea9-934d-c892384e0081 | ||||||
| TXT | 4b39cde4b0c178350793fa5fe4e6b79d7c3a1ed6 | ||||||
| TXT | f0095018235b8109a2bf9f65674a1784b6971ed6 | ||||||
| TXT | afternic-verification-4AQ5pU3CHThBNzvs3r7jmM | ||||||
| SOA | ns1.atom.comhostmaster@tidesensor.com 2026-03-27 #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=1782863416 | ||||||
Same first word
tidesensor.com |
Similar names
DNS History
7 records (3 active, 4 former)
●NSns1.atom.com2026-02-15 → 2026-07-01 · 3 obs
○ 2017-10-25 18:58:42
● 2026-02-15 19:58:00
● 2026-07-01 00:15:26
● 2026-02-15 19:58:00
● 2026-07-01 00:15:26
○NSns1.sedoparking.com2016-12-18 → 2017-10-25 · 4 obs
● 2016-12-18 21:00:40
● 2017-10-25 18:58:42
○ 2026-02-15 19:58:00
○ 2026-07-01 00:15:26
● 2017-10-25 18:58:42
○ 2026-02-15 19:58:00
○ 2026-07-01 00:15:26
●NSns2.atom.com2026-02-15 → 2026-07-01 · 3 obs
○ 2017-10-25 18:58:42
● 2026-02-15 19:58:00
● 2026-07-01 00:15:26
● 2026-02-15 19:58:00
● 2026-07-01 00:15:26
○NSns2.sedoparking.com2016-12-18 → 2017-10-25 · 4 obs
● 2016-12-18 21:00:40
● 2017-10-25 18:58:42
○ 2026-02-15 19:58:00
○ 2026-07-01 00:15:26
● 2017-10-25 18:58:42
○ 2026-02-15 19:58:00
○ 2026-07-01 00:15:26
○MXlocalhost2016-12-18 → 2026-02-15 · 4 obs
● 2016-12-18 21:00:40
● 2026-02-15 19:58:00
○ 2026-03-29 03:37:34
○ 2026-07-01 00:15:26
● 2026-02-15 19:58:00
○ 2026-03-29 03:37:34
○ 2026-07-01 00:15:26
●A52.20.84.622026-02-15 → 2026-07-01 · 3 obs
○ 2017-10-25 18:58:42
● 2026-02-15 19:58:00
● 2026-07-01 00:15:26
● 2026-02-15 19:58:00
● 2026-07-01 00:15:26
○A72.52.4.1192016-12-18 → 2017-10-25 · 4 obs
● 2016-12-18 21:00:40
● 2017-10-25 18:58:42
○ 2026-02-15 19:58:00
○ 2026-07-01 00:15:26
● 2017-10-25 18:58:42
○ 2026-02-15 19:58:00
○ 2026-07-01 00:15:26
🔍 DNS Trace
Analysis
IP Addresses
tidesensor.com points to a single IP number: 52.20.84.62.
Additional host names — ostbayern.com, binpilot.com, eduzine.com and two others — share IP numbers with tidesensor.com.
Name Servers
tidesensor.com is delegated to two name servers: ns1.atom.com and ns2.atom.com.
tidesensor.com shares its name server setup with other domains, including internext.com, pacificolab.com, logicrecruit.com and two others.
tidesensor.com has some name servers in common with other domains such as 235.co.in, vvims.com and nehaya.com
ns1.atom.com → 44.219.81.145 and ns2.atom.com → 50.19.240.86: one IP number per host name.