`securitybins.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.com`hostmaster@securitybins.com 2025-11-06 #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.net`nstld@verisign-grs.com serial=1774607892

Same first word

securitybins.com

DNS History

14 records (3 active, 11 former)

●NSns1.atom.com2026-02-15 → 2026-03-27 · 3 obs

○ 2017-03-22 00:21:58
● 2026-02-15 19:11:12
● 2026-03-27 11:05:38

●NSns2.atom.com2026-02-15 → 2026-03-27 · 3 obs

○ 2017-03-22 00:21:58
● 2026-02-15 19:11:12
● 2026-03-27 11:05:38

○NSns57.1and1.com2008-03-10 → 2008-03-10 · 3 obs

● 2008-03-10 00:28:40
○ 2015-10-10 17:29:04
○ 2026-03-27 11:05:38

○NSns58.1and1.com2008-03-10 → 2008-03-10 · 3 obs

● 2008-03-10 00:28:40
○ 2015-10-10 17:29:04
○ 2026-03-27 11:05:38

○NSrihana.ns.cloudflare.com2016-07-24 → 2017-03-22 · 5 obs

○ 2015-10-10 17:29:04
● 2016-07-24 22:51:56
● 2017-03-22 00:21:58
○ 2026-02-15 19:11:12
○ 2026-03-27 11:05:38

○NStony.ns.cloudflare.com2016-07-24 → 2017-03-22 · 5 obs

○ 2015-10-10 17:29:04
● 2016-07-24 22:51:56
● 2017-03-22 00:21:58
○ 2026-02-15 19:11:12
○ 2026-03-27 11:05:38

○MXmx00.1and1.com2008-03-10 → 2008-03-10 · 3 obs

● 2008-03-10 00:28:40
○ 2015-10-10 17:29:04
○ 2026-03-27 11:05:38

○MXmx01.1and1.com2008-03-10 → 2008-03-10 · 3 obs

● 2008-03-10 00:28:40
○ 2015-10-10 17:29:04
○ 2026-03-27 11:05:38

○A104.31.84.822016-07-24 → 2017-03-22 · 5 obs

○ 2015-10-10 17:29:04
● 2016-07-24 22:51:56
● 2017-03-22 00:21:58
○ 2026-02-15 19:11:12
○ 2026-03-27 11:05:38

○A104.31.85.822016-07-24 → 2017-03-22 · 5 obs

○ 2015-10-10 17:29:04
● 2016-07-24 22:51:56
● 2017-03-22 00:21:58
○ 2026-02-15 19:11:12
○ 2026-03-27 11:05:38

○A2400:cb00:2048:1::681f:54522016-07-24 → 2017-03-22 · 5 obs

○ 2015-10-10 17:29:04
● 2016-07-24 22:51:56
● 2017-03-22 00:21:58
○ 2026-02-15 19:11:12
○ 2026-03-27 11:05:38

○A2400:cb00:2048:1::681f:55522016-07-24 → 2017-03-22 · 5 obs

○ 2015-10-10 17:29:04
● 2016-07-24 22:51:56
● 2017-03-22 00:21:58
○ 2026-02-15 19:11:12
○ 2026-03-27 11:05:38

●A52.20.84.622026-02-15 → 2026-03-27 · 3 obs

○ 2017-03-22 00:21:58
● 2026-02-15 19:11:12
● 2026-03-27 11:05:38

○A74.208.61.1602008-03-10 → 2008-03-10 · 3 obs

● 2008-03-10 00:28:40
○ 2015-10-10 17:29:04
○ 2026-03-27 11:05:38

🔍 DNS Trace

Analysis

IP Addresses

securitybins.com points to a single IP address: 52.20.84.62.

Other host names such as feelsecure.org, strongup.com, coveworld.com, psyle.com and gudot.com share IPs with securitybins.com.

Name Servers

Two name servers ns1.atom.com and ns2.atom.com handle the delegation for securitybins.com.

securitybins.com shares the same name server setup as other domains, for example ledius.com, bet821.com, mindmailer.com, wrappedincloth.com and flixpod.com.

securitybins.com at least partially shares name servers with other domains, for example careerd.com, wybis.com, fontsmart.com, buildmuscle.in and bitcoiner.bet.

these name servers are commonly used alongside verification-yhehuhyrvixzqbtydgzisf.ns101.verify.hn name servers.

Host names with one IP number:

ns1.atom.com points to 44.219.81.145; ns2.atom.com points to 50.19.240.86.

securitybins.com - robtex.com