bitscore.in - dns.ninja

`bitscore.in`

DNSSEC	🔒 Signed (DS record present)
A	216.150.1.1^{🇨🇦 Amazon216.150.1.0/24 EC2 Prefix}
NS	`ns1.domaindiscount24.net` ⭐
		A	2a04:2b00:14cc::34^{🇬🇧 RCODEZERO-ANYCAST-SEC1-TLD2a04:2b00:14cc::/48}
			PTR	`ns1.monikerdns.net`
			PTR	`ns34.i.centralnic-dns.com`
		A	193.227.117.34^{🇩🇪 RCODEZERO-ANYCAST-SEC1-TLD193.227.117.0/24}
			PTR	`ns1.domaindiscount24.net`
NS	`ns2.domaindiscount24.net`
		A	2a04:2b00:14dd::34^{🇬🇧 RCODEZERO-ANYCAST-SEC22a04:2b00:14dd::/48}
			PTR	`ns2.monikerdns.net`
			PTR	`ns34.j.centralnic-dns.com`
		A	194.50.187.34^{🇩🇪 RCODEZERO-ANYCAST-SEC2194.50.187.0/24}
			PTR	`ns2.domaindiscount24.net`
NS	`ns3.domaindiscount24.net`
		A	2a04:2b00:14ee::34^{🇬🇧 RCODEZERO-ANYCAST-SEC22a04:2b00:14ee::/48}
			PTR	`ns3.monikerdns.net`
			PTR	`ns34.k.centralnic-dns.com`
		A	194.0.182.34^{🇩🇪 RCODEZERO-ANYCAST-SEC2194.0.182.0/24}
			PTR	`ns3.domaindiscount24.net`
MX	`smtp.google.com` ⭐
		A	2607:f8b0:4004:c17::1a^{🇺🇸 Google2607:f8b0:4004::/48}
			PTR	`bl-in-f26.1e100.net`
		A	2607:f8b0:4004:c1f::1a^{🇺🇸 Google2607:f8b0:4004::/48}
			PTR	`pd-in-f26.1e100.net`
		A	2607:f8b0:4004:c1f::1b^{🇺🇸 Google2607:f8b0:4004::/48}
			PTR	`pd-in-f27.1e100.net`
		A	2607:f8b0:4004:c21::1a^{🇺🇸 Google2607:f8b0:4004::/48}
			PTR	`pe-in-f26.1e100.net`
		A	64.233.180.26^{🇺🇸 Google64.233.180.0/24}
			PTR	`on-in-f26.1e100.net`
			PTR	`pe-in-f26.1e100.net`
		A	64.233.180.27^{🇺🇸 Google64.233.180.0/24}
			PTR	`on-in-f27.1e100.net`
			PTR	`pe-in-f27.1e100.net`
		A	142.251.16.27^{🇺🇸 Google142.251.16.0/24}
			PTR	`bl-in-f27.1e100.net`
		A	142.251.179.26^{🇺🇸 Google142.251.179.0/24}
			PTR	`pd-in-f26.1e100.net`
		A	142.251.179.27^{🇺🇸 Google142.251.179.0/24}
			PTR	`pd-in-f27.1e100.net`
TXT	`v=spf1 include:_spf.google.com include:zcsend.net ~all`
TXT	`linkedin-site-verification=333028fe-56d2-4128-ba42-64fefe047de2`
TXT	`v=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAsS9ag7/G4xKXcia...`
TXT	`zoho-verification=zb02577246.zmverify.zoho.com`
TXT	`google-site-verification=qlg-FUiES9dy55dFIjt-7nxZlyy2yaHiPvB8l-E1w_c`
SOA	`ns1.domaindiscount24.net`tech@key-systems.net serial=2026075760

`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=1786622157

Same first word

bitscore.in

bitscore.ca

bitscore.com

bitscore.net

bitscore.ai.in

bitscore.org

bitscore.ai

Similar names

DNS History

10 records (5 active, 5 former)

●NSns1.domaindiscount24.net2026-06-05 → 2026-08-13 · 2 obs

● 2026-06-05 14:06:28
● 2026-08-13 12:01:04

●NSns2.domaindiscount24.net2026-06-05 → 2026-08-13 · 2 obs

● 2026-06-05 14:06:28
● 2026-08-13 12:01:04

●NSns3.domaindiscount24.net2026-06-05 → 2026-08-13 · 2 obs

● 2026-06-05 14:06:28
● 2026-08-13 12:01:04

○MXalt1.aspmx.l.google.com2026-06-05 → 2026-06-05 · 3 obs

● 2026-06-05 14:06:28
○ 2026-08-13 12:01:02
○ 2026-08-13 12:01:04

○MXalt2.aspmx.l.google.com2026-06-05 → 2026-06-05 · 3 obs

● 2026-06-05 14:06:28
○ 2026-08-13 12:01:02
○ 2026-08-13 12:01:04

○MXaspmx.l.google.com2026-06-05 → 2026-06-05 · 3 obs

● 2026-06-05 14:06:28
○ 2026-08-13 12:01:02
○ 2026-08-13 12:01:04

○MXaspmx2.googlemail.com2026-06-05 → 2026-06-05 · 3 obs

● 2026-06-05 14:06:28
○ 2026-08-13 12:01:02
○ 2026-08-13 12:01:04

○MXaspmx3.googlemail.com2026-06-05 → 2026-06-05 · 3 obs

● 2026-06-05 14:06:28
○ 2026-08-13 12:01:02
○ 2026-08-13 12:01:04

●MXsmtp.google.com2026-08-13 → 2026-08-13 · 3 obs

○ 2026-06-05 14:06:28
● 2026-08-13 12:01:02
● 2026-08-13 12:01:04

●A216.150.1.12026-06-05 → 2026-08-13 · 2 obs

● 2026-06-05 14:06:28
● 2026-08-13 12:01:04

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
in	ns3.registry.in, ns1.registry.in, ns2.registry.in, ns4.registry.in	-
bitscore.in	ns1.domaindiscount24.net, ns2.domaindiscount24.net, ns3.domaindiscount24.net	-

✅ Authoritative Response

Server:193.227.117.34

NS records: ns1.domaindiscount24.net, ns2.domaindiscount24.net, ns3.domaindiscount24.net

🔒 DNSSEC Status

🔐 Secure (DNSSEC validated)

Chain of trust verified from root to domain

⏱️ Timing

Total: 429ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`216.150.1.1`
NS	3	`ns3.domaindiscount24.net, ns1.domaindiscount24.net...`
MX	1	`smtp.google.com (pri: 1)`
TXT	5	`linkedin-site-verification=333028fe-56d2, zoho-verification=zb02577246.zmverify.zo...`
SOA	1	`ns1.domaindiscount24.net tech.key-system`

Analysis

IP Addresses

bitscore.in resolves to one IP address: 216.150.1.1.

meibc.co.za, hurricanebaptist.org, rayelder.com and two other host names share IP numbers with bitscore.in.

Name Servers

bitscore.in is delegated to three name servers: ns1.domaindiscount24.net, ns2.domaindiscount24.net and ns3.domaindiscount24.net.

bitscore.in has at least partial name server overlap with other domains, such as isonet.at, go-greener.eu, inform-software.eu and two others.

ns1.domaindiscount24.net, ns2.domaindiscount24.net and ns3.domaindiscount24.net each resolve to two IP addresses: ns1.domaindiscount24.net resolves to 193.227.117.34 and 2a04:2b00:14cc::34; ns2.domaindiscount24.net resolves to 194.50.187.34 and 2a04:2b00:14dd::34; ns3.domaindiscount24.net resolves to 194.0.182.34 and 2a04:2b00:14ee::34.

Mail Servers

Mail for bitscore.in is handled by a single mail server, smtp.google.com.

bitscore.in uses an identical mail server configuration to several other domains — among them palmettoparents.com, martins.co.in, familyof(0x356578)pressservices.com and two more.

bitscore.in has at least partial mail server overlap with other domains such as ivsa.org, neer.ai, shreyasprojects.com and two more.

These mail servers commonly appear together with alt1.aspmx.l.google.com, alt2.aspmx.l.google.com, aspmx.l.google.com and two other mail servers.

smtp.google.com resolves to 9 IP addresses — 64.233.180.26, 64.233.180.27, 142.251.16.27 and 6 others.