techcom.in - robtex.com

techcom.in

DNSSEC⚠️ Not signed
A64.190.63.222🇩🇪 SEDO64.190.62.0/23 -NET2-PI
NSns1.sedoparking.com
A3.130.216.63🇺🇸 Amazon3.130.0.0/16 EC2 CMH prefix
PTRec2-3-130-216-63.us-east-2.compute.amazonaws.com
A91.195.241.8🇩🇪 SEDO91.195.240.0/23 -NET-PI
NSns2.sedoparking.com
A34.211.188.210🇺🇸 Amazon34.208.0.0/12 EC2 PDX prefix
PTRec2-34-211-188-210.us-west-2.compute.amazonaws.com
A91.195.240.8🇩🇪 SEDO91.195.240.0/23 -NET-PI
MXlocalhost
TXTv=spf1 -all
SOAns1.sedoparking.comhostmaster@sedo.de 2018-05-16 #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=1784951152

Same first word

Similar names

DNS History

22 records (4 active, 18 former)

2017201820192020202120222023202420252026NSns1.sedoparking.comns2.sedoparking.comns1.888dns.netns1.dnskarma.comns1.v6nameserver.comns2.888dns.netns2.dnskarma.comns2.v6nameserver.comns3.888dns.netns3.dnskarma.comns3.v6nameserver.comns4.888dns.netns4.v6nameserver.comns71.domaincontrol.comns72.domaincontrol.comMXlocalhostA64.190.63.22213.234.51.109213.184.126.1622a00:7c80:0:69::286.107.110.24793.190.140.242
NSns1.888dns.net2016-03-21 → 2016-03-21 · 3 obs
● 2016-03-21 03:18:02
○ 2016-08-10 18:52:28
○ 2026-07-25 03:54:50
NSns1.dnskarma.com2016-08-10 → 2016-08-10 · 4 obs
○ 2016-03-21 03:18:02
● 2016-08-10 18:52:28
○ 2017-04-11 22:20:24
○ 2026-07-25 03:54:50
NSns1.sedoparking.com2026-06-14 → 2026-07-25 · 3 obs
○ 2021-09-12 10:15:48
● 2026-06-14 01:13:54
● 2026-07-25 03:54:50
NSns1.v6nameserver.com2017-04-11 → 2017-04-11 · 4 obs
○ 2016-08-10 18:52:28
● 2017-04-11 22:20:24
○ 2021-09-12 10:15:48
○ 2026-07-25 03:54:50
NSns2.888dns.net2016-03-21 → 2016-03-21 · 3 obs
● 2016-03-21 03:18:02
○ 2016-08-10 18:52:28
○ 2026-07-25 03:54:50
NSns2.dnskarma.com2016-08-10 → 2016-08-10 · 4 obs
○ 2016-03-21 03:18:02
● 2016-08-10 18:52:28
○ 2017-04-11 22:20:24
○ 2026-07-25 03:54:50
NSns2.sedoparking.com2026-06-14 → 2026-07-25 · 3 obs
○ 2021-09-12 10:15:48
● 2026-06-14 01:13:54
● 2026-07-25 03:54:50
NSns2.v6nameserver.com2017-04-11 → 2017-04-11 · 4 obs
○ 2016-08-10 18:52:28
● 2017-04-11 22:20:24
○ 2021-09-12 10:15:48
○ 2026-07-25 03:54:50
NSns3.888dns.net2016-03-21 → 2016-03-21 · 3 obs
● 2016-03-21 03:18:02
○ 2016-08-10 18:52:28
○ 2026-07-25 03:54:50
NSns3.dnskarma.com2016-08-10 → 2016-08-10 · 4 obs
○ 2016-03-21 03:18:02
● 2016-08-10 18:52:28
○ 2017-04-11 22:20:24
○ 2026-07-25 03:54:50
NSns3.v6nameserver.com2017-04-11 → 2017-04-11 · 4 obs
○ 2016-08-10 18:52:28
● 2017-04-11 22:20:24
○ 2021-09-12 10:15:48
○ 2026-07-25 03:54:50
NSns4.888dns.net2016-03-21 → 2016-03-21 · 3 obs
● 2016-03-21 03:18:02
○ 2016-08-10 18:52:28
○ 2026-07-25 03:54:50
NSns4.v6nameserver.com2017-04-11 → 2017-04-11 · 4 obs
○ 2016-08-10 18:52:28
● 2017-04-11 22:20:24
○ 2021-09-12 10:15:48
○ 2026-07-25 03:54:50
NSns71.domaincontrol.com2021-09-12 → 2021-09-12 · 4 obs
○ 2017-04-11 22:20:24
● 2021-09-12 10:15:48
○ 2026-06-14 01:13:54
○ 2026-07-25 03:54:50
NSns72.domaincontrol.com2021-09-12 → 2021-09-12 · 4 obs
○ 2017-04-11 22:20:24
● 2021-09-12 10:15:48
○ 2026-06-14 01:13:54
○ 2026-07-25 03:54:50
MXlocalhost2026-06-14 → 2026-07-25 · 2 obs
● 2026-06-14 01:13:54
● 2026-07-25 03:54:50
A13.234.51.1092021-09-12 → 2021-09-12 · 4 obs
○ 2017-04-11 22:20:24
● 2021-09-12 10:15:48
○ 2026-06-14 01:13:54
○ 2026-07-25 03:54:50
A213.184.126.1622016-03-21 → 2016-03-21 · 3 obs
● 2016-03-21 03:18:02
○ 2016-08-10 18:52:28
○ 2026-07-25 03:54:50
A2a00:7c80:0:69::22017-04-11 → 2017-04-11 · 4 obs
○ 2016-08-10 18:52:28
● 2017-04-11 22:20:24
○ 2021-09-12 10:15:48
○ 2026-07-25 03:54:50
A64.190.63.2222026-06-14 → 2026-07-25 · 3 obs
○ 2021-09-12 10:15:48
● 2026-06-14 01:13:54
● 2026-07-25 03:54:50
A86.107.110.2472016-08-10 → 2016-08-10 · 4 obs
○ 2016-03-21 03:18:02
● 2016-08-10 18:52:28
○ 2017-04-11 22:20:24
○ 2026-07-25 03:54:50
A93.190.140.2422017-04-11 → 2017-04-11 · 4 obs
○ 2016-08-10 18:52:28
● 2017-04-11 22:20:24
○ 2021-09-12 10:15:48
○ 2026-07-25 03:54:50

🔍 DNS Trace

📋 Delegation Chain

ZoneNameserversGlue
inns1.registry.in, ns4.registry.in, ns3.registry.in, ns2.registry.in-
techcom.inns1.sedoparking.com, ns2.sedoparking.com-

✅ Authoritative Response

Server:3.130.216.63

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

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for techcom.in (unsigned zone)

⏱️ Timing

Total: 462ms | Queries: -

📄 Records

TypeCountSample Data
A164.190.63.222
NS2ns1.sedoparking.com, ns2.sedoparking.com
MX1localhost (pri: 0)
TXT1v=spf1 -all
SOA1ns1.sedoparking.com hostmaster.sedo.de

Analysis

IP Addresses

techcom.in has exactly one IP address — 64.190.63.222.

gyk.it, halifax.attemptedlogin.com, calamares.es plus two other host names have IP numbers in common with techcom.in.

Name Servers

DNS delegation for techcom.in points to two name servers: ns1.sedoparking.com and ns2.sedoparking.com.

The name server configuration of techcom.in is shared with other domains, for instance mail.to-ur.com, (0x736578)finder.at, bt.touchtablet.de and two others.

Some of techcom.in's name servers are also used by other domains, including cheapmotorcar.com, auto-ibuvirus.blogspot.com.ua, auto-badutseolucu.blogspot.com.ua and welld.de.

These name servers are regularly seen alongside ns3.sedoparking.com and ns4.sedoparking.com as name servers.

ns1.sedoparking.com directs to 3.130.216.63 and 91.195.241.8. ns2.sedoparking.com directs to 34.211.188.210 and 91.195.240.8. Each host name carries two IP addresses.

Mail Servers

techcom.in uses one mail server — localhost.

The mail server setup of techcom.in matches that of other domains such as logiccore.com, instafx.de, dopage.org and two others.