securitytech.in - dns.ninja

securitytech.in

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
SOAns1.atom.comhostmaster@securitytech.in 2025-11-12 #1

in

DNSSEC🔒 Signed (DS record present)
NSns.trs-dns.com ⭐
NSns1.registry.in
NSns2.registry.in
NSns3.registry.in
NSns4.registry.in
SOAns.trs-dns.comtrs-ops@tucows.com serial=17856(0x37313735)1

Same first word

securitytech.cl
securitytech.in
securitytech.gr
securitytech.com.mx
securitytech.io
securitytech.net
securitytech.org
securitytech.ca

Similar names

techsecurity.com.au
techsecurity.com.sg
techsecurity.net

DNS History

22 records (3 active, 19 former)

20162017201820192020202120222023202420252026NSns1.atom.comns2.atom.comdns17.parkpage.foundationapi.comdns18.parkpage.foundationapi.comlaunch1.spaceship.netlaunch2.spaceship.netns.securitytech.inns01.domaincontrol.comns02.domaincontrol.comns1.bh-plesk-web3.webhostbox.netns2.bh-plesk-web3.webhostbox.netMXalt1.aspmx.l.google.comalt2.aspmx.l.google.comaspmx.l.google.commailstore1.secureserver.netsmtp.secureserver.netA52.20.84.62184.168.221.53199.79.63.188209.99.40.22644.233.250.7552.38.196.63
○NSdns17.parkpage.foundationapi.com2016-02-04 → 2016-02-04 · 4 obs
○ 2015-11-13 21:38:48
● 2016-02-04 10:53:00
○ 2016-04-27 22:01:08
○ 2026-08-02 12:37:10
○NSdns18.parkpage.foundationapi.com2016-02-04 → 2016-02-04 · 4 obs
○ 2015-11-13 21:38:48
● 2016-02-04 10:53:00
○ 2016-04-27 22:01:08
○ 2026-08-02 12:37:10
○NSlaunch1.spaceship.net2026-04-13 → 2026-08-02 · 2 obs
○ 2026-04-13 19:24:28
○ 2026-08-02 12:37:10
○NSlaunch2.spaceship.net2026-04-13 → 2026-08-02 · 2 obs
○ 2026-04-13 19:24:28
○ 2026-08-02 12:37:10
○NSns.securitytech.in2015-07-11 → 2015-11-13 · 4 obs
● 2015-07-11 08:57:04
● 2015-11-13 21:38:48
○ 2016-02-04 10:53:00
○ 2026-08-02 12:37:10
○NSns01.domaincontrol.com2017-03-23 → 2017-03-23 · 4 obs
○ 2016-04-27 22:01:08
● 2017-03-23 01:33:36
○ 2026-04-13 19:24:28
○ 2026-08-02 12:37:10
○NSns02.domaincontrol.com2017-03-23 → 2017-03-23 · 4 obs
○ 2016-04-27 22:01:08
● 2017-03-23 01:33:36
○ 2026-04-13 19:24:28
○ 2026-08-02 12:37:10
●NSns1.atom.com2026-04-13 → 2026-08-02 · 3 obs
○ 2017-03-23 01:33:36
● 2026-04-13 19:24:28
● 2026-08-02 12:37:10
○NSns1.bh-plesk-web3.webhostbox.net2015-07-11 → 2015-11-13 · 4 obs
● 2015-07-11 08:57:04
● 2015-11-13 21:38:48
○ 2016-02-04 10:53:00
○ 2026-08-02 12:37:10
●NSns2.atom.com2026-04-13 → 2026-08-02 · 3 obs
○ 2017-03-23 01:33:36
● 2026-04-13 19:24:28
● 2026-08-02 12:37:10
○NSns2.bh-plesk-web3.webhostbox.net2015-07-11 → 2015-11-13 · 4 obs
● 2015-07-11 08:57:04
● 2015-11-13 21:38:48
○ 2016-02-04 10:53:00
○ 2026-08-02 12:37:10
○MXalt1.aspmx.l.google.com2015-07-11 → 2015-11-13 · 4 obs
● 2015-07-11 08:57:04
● 2015-11-13 21:38:48
○ 2016-02-04 10:53:00
○ 2026-08-02 12:37:10
○MXalt2.aspmx.l.google.com2015-07-11 → 2015-11-13 · 4 obs
● 2015-07-11 08:57:04
● 2015-11-13 21:38:48
○ 2016-02-04 10:53:00
○ 2026-08-02 12:37:10
○MXaspmx.l.google.com2015-07-11 → 2015-11-13 · 4 obs
● 2015-07-11 08:57:04
● 2015-11-13 21:38:48
○ 2016-02-04 10:53:00
○ 2026-08-02 12:37:10
○MXmailstore1.secureserver.net2017-03-23 → 2017-03-23 · 4 obs
○ 2016-02-04 10:53:00
● 2017-03-23 01:33:36
○ 2026-04-13 19:24:28
○ 2026-08-02 12:37:10
○MXsmtp.secureserver.net2017-03-23 → 2017-03-23 · 4 obs
○ 2016-02-04 10:53:00
● 2017-03-23 01:33:36
○ 2026-04-13 19:24:28
○ 2026-08-02 12:37:10
○A184.168.221.532017-03-23 → 2017-03-23 · 4 obs
○ 2016-04-27 22:01:08
● 2017-03-23 01:33:36
○ 2026-04-13 19:24:28
○ 2026-08-02 12:37:10
○A199.79.63.1882015-07-11 → 2015-11-13 · 4 obs
● 2015-07-11 08:57:04
● 2015-11-13 21:38:48
○ 2016-02-04 10:53:00
○ 2026-08-02 12:37:10
○A209.99.40.2262016-02-04 → 2016-02-04 · 4 obs
○ 2015-11-13 21:38:48
● 2016-02-04 10:53:00
○ 2016-04-27 22:01:08
○ 2026-08-02 12:37:10
○A44.233.250.752026-04-13 → 2026-08-02 · 2 obs
○ 2026-04-13 19:24:28
○ 2026-08-02 12:37:10
●A52.20.84.622026-04-13 → 2026-08-02 · 3 obs
○ 2017-03-23 01:33:36
● 2026-04-13 19:24:28
● 2026-08-02 12:37:10
○A52.38.196.632026-04-13 → 2026-08-02 · 2 obs
○ 2026-04-13 19:24:28
○ 2026-08-02 12:37:10

🔍 DNS Trace

📋 Delegation Chain

ZoneNameserversGlue
inns2.registry.in, ns3.registry.in, ns4.registry.in, ns1.registry.in-
securitytech.inns2.atom.com, ns1.atom.com-

✅ Authoritative Response

Server:44.219.81.145

NS records: ns2.atom.com, ns1.atom.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for securitytech.in (unsigned zone)

⏱️ Timing

Total: 193ms | Queries: -

📄 Records

TypeCountSample Data
A152.20.84.62
NS2ns2.atom.com, ns1.atom.com
SOA1ns1.atom.com hostmaster.securitytech.in

Analysis

IP Addresses

securitytech.in resolves to one IP address: 52.20.84.62.

medoko.com, eclans.com, bikingfun.com and two other host names share IP numbers with securitytech.in.

Name Servers

DNS delegation for securitytech.in points to two name servers: ns1.atom.com and ns2.atom.com.

securitytech.in uses the same name servers as several other domains — among them nestmatic.com, eachbit.com, copyrighttoday.com and two more.

securitytech.in has at least partial name server overlap with other domains, such as trulv.com, syntaxin.com, wpqj.com and two others.

It is common to find these name servers paired with the name servers verification-j8yfce5btmdxy4vrwdyypd.ns101.verify.hn.

ns1.atom.com directs to 44.219.81.145 and ns2.atom.com directs to 50.19.240.86; each host name points to exactly one IP number.