shieldsure.com - dns.ninja

shieldsure.com

DNSSEC⚠️ Not signed
A52.20.84.62πŸ‡ΊπŸ‡Έ Amazon52.20.0.0/14 EC2 IAD prefix
PTRec2-52-20-84-62.compute-1.amazonaws.com
NSns1.atom.com ⭐
A44.219.81.145πŸ‡ΊπŸ‡Έ Amazon44.192.0.0/11 EC2 IAD prefix
PTRec2-44-219-81-145.compute-1.amazonaws.com
NSns2.atom.com
A50.19.240.86πŸ‡ΊπŸ‡Έ Amazon50.19.128.0/17 EC2 IAD prefix
PTRec2-50-19-240-86.compute-1.amazonaws.com
TXTf0095018235b8109a2bf9f65674a1784b6971ed6
SOAns1.atom.comhostmaster@shieldsure.com 2025-11-07 #1

com

WOT: SAFE (40/100)

Subdomains

Same first word

Similar names

DNS History

23 records (3 active, 20 former)

20162017201820192020202120222023202420252026NSns1.atom.comns2.atom.comns-1174.awsdns-18.orgns-1958.awsdns-52.co.ukns-444.awsdns-55.comns-925.awsdns-51.netns01.domaincontrol.comns02.domaincontrol.comMXalt1.aspmx.l.google.comalt2.aspmx.l.google.comaspmx.l.google.comaspmx2.googlemail.comaspmx3.googlemail.commailstore1.secureserver.netmx.zoho.commx2.zoho.commx3.zoho.comsmtp.secureserver.netA52.20.84.62184.168.221.4752.201.31.24752.55.221.20PTRsmtp.zoho.com
β—‹NSns-1174.awsdns-18.org2017-04-18 β†’ 2017-04-18 Β· 4 obs
β—‹ 2016-09-19 20:31:30
● 2017-04-18 10:46:26
β—‹ 2026-02-26 05:36:16
β—‹ 2026-06-10 19:06:36
β—‹NSns-1958.awsdns-52.co.uk2017-04-18 β†’ 2017-04-18 Β· 4 obs
β—‹ 2016-09-19 20:31:30
● 2017-04-18 10:46:26
β—‹ 2026-02-26 05:36:16
β—‹ 2026-06-10 19:06:36
β—‹NSns-444.awsdns-55.com2017-04-18 β†’ 2017-04-18 Β· 4 obs
β—‹ 2016-09-19 20:31:30
● 2017-04-18 10:46:26
β—‹ 2026-02-26 05:36:16
β—‹ 2026-06-10 19:06:36
β—‹NSns-925.awsdns-51.net2017-04-18 β†’ 2017-04-18 Β· 4 obs
β—‹ 2016-09-19 20:31:30
● 2017-04-18 10:46:26
β—‹ 2026-02-26 05:36:16
β—‹ 2026-06-10 19:06:36
β—‹NSns01.domaincontrol.com2015-10-24 β†’ 2016-09-19 Β· 4 obs
● 2015-10-24 01:50:36
● 2016-09-19 20:31:30
β—‹ 2017-04-18 10:46:26
β—‹ 2026-06-10 19:06:36
β—‹NSns02.domaincontrol.com2015-10-24 β†’ 2016-09-19 Β· 4 obs
● 2015-10-24 01:50:36
● 2016-09-19 20:31:30
β—‹ 2017-04-18 10:46:26
β—‹ 2026-06-10 19:06:36
●NSns1.atom.com2026-02-26 β†’ 2026-06-10 Β· 3 obs
β—‹ 2017-04-18 10:46:26
● 2026-02-26 05:36:16
● 2026-06-10 19:06:36
●NSns2.atom.com2026-02-26 β†’ 2026-06-10 Β· 3 obs
β—‹ 2017-04-18 10:46:26
● 2026-02-26 05:36:16
● 2026-06-10 19:06:36
β—‹MXalt1.aspmx.l.google.com2016-04-09 β†’ 2016-04-09 Β· 4 obs
β—‹ 2016-01-15 09:00:06
● 2016-04-09 07:32:02
β—‹ 2016-09-19 20:31:30
β—‹ 2026-06-10 19:06:36
β—‹MXalt2.aspmx.l.google.com2016-04-09 β†’ 2016-04-09 Β· 4 obs
β—‹ 2016-01-15 09:00:06
● 2016-04-09 07:32:02
β—‹ 2016-09-19 20:31:30
β—‹ 2026-06-10 19:06:36
β—‹MXaspmx.l.google.com2016-04-09 β†’ 2016-04-09 Β· 4 obs
β—‹ 2016-01-15 09:00:06
● 2016-04-09 07:32:02
β—‹ 2016-09-19 20:31:30
β—‹ 2026-06-10 19:06:36
β—‹MXaspmx2.googlemail.com2016-04-09 β†’ 2016-04-09 Β· 4 obs
β—‹ 2016-01-15 09:00:06
● 2016-04-09 07:32:02
β—‹ 2016-09-19 20:31:30
β—‹ 2026-06-10 19:06:36
β—‹MXaspmx3.googlemail.com2016-04-09 β†’ 2016-04-09 Β· 4 obs
β—‹ 2016-01-15 09:00:06
● 2016-04-09 07:32:02
β—‹ 2016-09-19 20:31:30
β—‹ 2026-06-10 19:06:36
β—‹MXmailstore1.secureserver.net2015-10-24 β†’ 2016-01-15 Β· 4 obs
● 2015-10-24 01:50:36
● 2016-01-15 09:00:06
β—‹ 2016-04-09 07:32:02
β—‹ 2026-06-10 19:06:36
β—‹MXmx.zoho.com2016-09-19 β†’ 2017-04-18 Β· 5 obs
β—‹ 2016-04-09 07:32:02
● 2016-09-19 20:31:30
● 2017-04-18 10:46:26
β—‹ 2026-02-26 05:36:16
β—‹ 2026-06-10 19:06:36
β—‹MXmx2.zoho.com2016-09-19 β†’ 2017-04-18 Β· 5 obs
β—‹ 2016-04-09 07:32:02
● 2016-09-19 20:31:30
● 2017-04-18 10:46:26
β—‹ 2026-02-26 05:36:16
β—‹ 2026-06-10 19:06:36
β—‹MXmx3.zoho.com2017-04-18 β†’ 2017-04-18 Β· 4 obs
β—‹ 2016-09-19 20:31:30
● 2017-04-18 10:46:26
β—‹ 2026-02-26 05:36:16
β—‹ 2026-06-10 19:06:36
β—‹MXsmtp.secureserver.net2015-10-24 β†’ 2016-01-15 Β· 4 obs
● 2015-10-24 01:50:36
● 2016-01-15 09:00:06
β—‹ 2016-04-09 07:32:02
β—‹ 2026-06-10 19:06:36
β—‹A184.168.221.472015-10-24 β†’ 2016-01-15 Β· 4 obs
● 2015-10-24 01:50:36
● 2016-01-15 09:00:06
β—‹ 2016-04-09 07:32:02
β—‹ 2026-06-10 19:06:36
●A52.20.84.622026-02-26 β†’ 2026-06-10 Β· 3 obs
β—‹ 2017-04-18 10:46:26
● 2026-02-26 05:36:16
● 2026-06-10 19:06:36
β—‹A52.201.31.2472016-04-09 β†’ 2016-09-19 Β· 5 obs
β—‹ 2016-01-15 09:00:06
● 2016-04-09 07:32:02
● 2016-09-19 20:31:30
β—‹ 2017-04-18 10:46:26
β—‹ 2026-06-10 19:06:36
β—‹A52.55.221.202017-04-18 β†’ 2017-04-18 Β· 4 obs
β—‹ 2016-09-19 20:31:30
● 2017-04-18 10:46:26
β—‹ 2026-02-26 05:36:16
β—‹ 2026-06-10 19:06:36
β—‹PTRsmtp.zoho.com2017-04-18 β†’ 2017-04-18 Β· 3 obs
● 2017-04-18 10:46:26
β—‹ 2026-02-26 05:36:16
β—‹ 2026-06-10 19:06:36

πŸ” DNS Trace

Analysis

Hierarchy

shieldsure.com is the parent zone for www.shieldsure.com.

IP Addresses

shieldsure.com directs to one IP number, which is 52.20.84.62.

Among the host names that share IP numbers with shieldsure.com are leadlab.net, biokul.com, wqwq.com and two others.

Name Servers

shieldsure.com has two authoritative name servers β€” ns1.atom.com and ns2.atom.com.

shieldsure.com has the same name server delegation as a number of other domains, such as zipturbo.com, interactsy.com, blockfiling.com and two more.

shieldsure.com at least partially shares name servers with other domains, for instance vimbel.com, akuma.com and roamfix.com.

These name servers often co-occur with the name servers verification-jqqeszsxf3b5xjj5w7lefh.ns101.verify.hn.

ns1.atom.com resolves to 44.219.81.145. ns2.atom.com resolves to 50.19.240.86. Both host names point to a single IP number.