`elecbits.in`

DNSSEC	⚠️ Not signed
A	65.2.141.200^{🇮🇳 Amazon65.0.0.0/14 EC2 BOM prefix}
		PTR	`ec2-65-2-141-200.ap-south-1.compute.amazonaws.com`
NS	`ns11.domaincontrol.com` ⭐
		A	2603:5:2190::6^{🇺🇸 GODADDY-DNS2603:5:2190::/44}
			PTR	`ns11.domaincontrol.com`
		A	97.74.105.6^{🇺🇸 GODADDY-DNS97.74.104.0/23}
			PTR	`ns11.domaincontrol.com`
NS	`ns12.domaincontrol.com`
		A	2603:5:2290::6^{🇺🇸 GODADDY-DNS2603:5:2290::/44}
			PTR	`ns12.domaincontrol.com`
		A	173.201.73.6^{🇺🇸 GODADDY-DNS173.201.72.0/23}
			PTR	`ns12.domaincontrol.com`
MX	`aspmx.l.google.com` ⭐
		A	2607:f8b0:4004:c1b::1a^{🇺🇸 Google2607:f8b0:4004::/48}
			PTR	`wv-in-f26.1e100.net`
		A	142.250.31.27^{🇺🇸 Google142.250.31.0/24}
			PTR	`bj-in-f27.1e100.net`
MX	`alt1.aspmx.l.google.com`⁽⁵⁾
		A	2800:3f0:4003:c0f::1a^{🇨🇱 Google2800:3f0:4003::/48}
		A	108.177.123.26^{🇺🇸 Google108.177.123.0/24}
			PTR	`lcscld-in-f26.1e100.net`
MX	`alt2.aspmx.l.google.com`⁽⁵⁾
		A	2a00:1450:400b:c01::1a^{🇮🇪 Google2a00:1450:400b::/48}
			PTR	`di-in-f26.1e100.net`
		A	74.125.193.27^{🇺🇸 Google74.125.193.0/24}
			PTR	`di-in-f27.1e100.net`
			PTR	`ig-in-f27.1e100.net`
MX	`alt3.aspmx.l.google.com`⁽¹⁰⁾
		A	2a00:1450:4009:c0f::1b^{🇬🇧 Google2a00:1450:4009::/48}
			PTR	`yulhrs-in-f27.1e100.net`
		A	192.178.223.26^{🇺🇸 Google192.178.223.0/24}
			PTR	`yulhrs-in-f26.1e100.net`
MX	`alt4.aspmx.l.google.com`⁽¹⁰⁾
		A	2a00:1450:400c:c23::1a^{🇧🇪 Google2a00:1450:400c::/48}
			PTR	`yubrupd-in-f26.1e100.net`
		A	172.253.157.26^{🇺🇸 Google172.253.0.0/16}
			PTR	`yubrupd-in-f26.1e100.net`
TXT	`linkedin-site-verification=eb0e6ee1-6304-40e8-b529-040f64c6b539`
TXT	`v=spf1 include:_spf.google.com ~all`
TXT	`google-site-verification=ejvXI9VXsONDz5oR6uX2-cMMoeaoaq1Oe10hkeoa1U0`
SOA	`ns11.domaincontrol.com`dns@jomax.net 2026-06-14 #1

`in`

	DNSSEC	🔒 Signed (DS record present)
	NS	`ns.trs-dns.com` ⭐
	NS	`ns1.registry.in`
	NS	`ns2.registry.in`
	NS	`ns3.registry.in`
	NS	`ns4.registry.in`
	SOA	`ns.trs-dns.com`trs-ops@tucows.com serial=1785475257

⚠️ On DNS blocklist: tif
🦠 Blackbook: Known malware/C&C domain

Same first word

elecbits.in

Similar names

DNS History

14 records (8 active, 6 former)

○NSben.ns.cloudflare.com2017-03-16 → 2017-03-16 · 3 obs

● 2017-03-16 17:35:22
○ 2026-05-09 08:01:46
○ 2026-07-31 06:05:28

●NSns11.domaincontrol.com2026-05-09 → 2026-07-31 · 3 obs

○ 2017-03-16 17:35:22
● 2026-05-09 08:01:46
● 2026-07-31 06:05:28

●NSns12.domaincontrol.com2026-05-09 → 2026-07-31 · 3 obs

○ 2017-03-16 17:35:22
● 2026-05-09 08:01:46
● 2026-07-31 06:05:28

○NSolga.ns.cloudflare.com2017-03-16 → 2017-03-16 · 3 obs

● 2017-03-16 17:35:22
○ 2026-05-09 08:01:46
○ 2026-07-31 06:05:28

●MXalt1.aspmx.l.google.com2026-05-09 → 2026-07-31 · 2 obs

● 2026-05-09 08:01:46
● 2026-07-31 06:05:28

●MXalt2.aspmx.l.google.com2026-05-09 → 2026-07-31 · 2 obs

● 2026-05-09 08:01:46
● 2026-07-31 06:05:28

●MXalt3.aspmx.l.google.com2026-05-09 → 2026-07-31 · 2 obs

● 2026-05-09 08:01:46
● 2026-07-31 06:05:28

●MXalt4.aspmx.l.google.com2026-05-09 → 2026-07-31 · 2 obs

● 2026-05-09 08:01:46
● 2026-07-31 06:05:28

●MXaspmx.l.google.com2026-05-09 → 2026-07-31 · 2 obs

● 2026-05-09 08:01:46
● 2026-07-31 06:05:28

○A104.31.86.822017-03-16 → 2017-03-16 · 3 obs

● 2017-03-16 17:35:22
○ 2026-05-09 08:01:46
○ 2026-07-31 06:05:28

○A104.31.87.822017-03-16 → 2017-03-16 · 3 obs

● 2017-03-16 17:35:22
○ 2026-05-09 08:01:46
○ 2026-07-31 06:05:28

○A2400:cb00:2048:1::681f:56522017-03-16 → 2017-03-16 · 3 obs

● 2017-03-16 17:35:22
○ 2026-05-09 08:01:46
○ 2026-07-31 06:05:28

○A2400:cb00:2048:1::681f:57522017-03-16 → 2017-03-16 · 3 obs

● 2017-03-16 17:35:22
○ 2026-05-09 08:01:46
○ 2026-07-31 06:05:28

●A65.2.141.2002026-05-09 → 2026-07-31 · 3 obs

○ 2017-03-16 17:35:22
● 2026-05-09 08:01:46
● 2026-07-31 06:05:28

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
in	ns4.registry.in, ns1.registry.in, ns2.registry.in, ns3.registry.in	-
elecbits.in	ns11.domaincontrol.com, ns12.domaincontrol.com	-

✅ Authoritative Response

Server:97.74.105.6

NS records: ns11.domaincontrol.com, ns12.domaincontrol.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for elecbits.in (unsigned zone)

⏱️ Timing

Total: 1336ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`65.2.141.200`
NS	2	`ns11.domaincontrol.com, ns12.domaincontrol.com`
MX	5	`aspmx.l.google.com (pri: 1), alt1.aspmx.l.google.com (pri: 5)...`
TXT	3	`linkedin-site-verification=eb0e6ee1-6304, v=spf1 include:_spf.google.com ~all...`
SOA	1	`ns11.domaincontrol.com dns.jomax.net`

Analysis

IP Addresses

elecbits.in resolves to one IP address: 65.2.141.200.

Name Servers

elecbits.in uses two name servers for its delegation: ns11.domaincontrol.com and ns12.domaincontrol.com.

elecbits.in uses the same name servers as several other domains — among them thunderguild.com, nursengo.com, mvhltc.com and two more.

The two host names ns11.domaincontrol.com and ns12.domaincontrol.com each have a pair of IP addresses: ns11.domaincontrol.com has 97.74.105.6 and 2603:5:2190::6, and ns12.domaincontrol.com has 173.201.73.6 and 2603:5:2290::6.

Mail Servers

elecbits.in has five mail servers, which are aspmx.l.google.com, alt1.aspmx.l.google.com, alt2.aspmx.l.google.com and two others.

elecbits.in has at least partial mail server overlap with other domains such as vincentjamesmentoring.com, kirangroupofcompanies.com, pointone.digital and two more.

The mail servers alt3.aspmx.l.google.com, alt4.aspmx.l.google.com, aspmx2.googlemail.com and aspmx3.googlemail.com are commonly seen alongside these mail servers.

Hostnames that resolve to two IP addresses:

aspmx.l.google.com directs traffic to 142.250.31.27 and 2607:f8b0:4004:c1b::1a.

alt1.aspmx.l.google.com directs traffic to 108.177.123.26 and 2800:3f0:4003:c0f::1a.

alt2.aspmx.l.google.com directs traffic to 74.125.193.27 and 2a00:1450:400b:c01::1a.

alt3.aspmx.l.google.com directs traffic to 192.178.223.26 and 2a00:1450:4009:c0f::1b.

alt4.aspmx.l.google.com directs traffic to 172.253.157.26 and 2a00:1450:400c:c23::1a.