indscope.com - dns.ninja

`indscope.com`

DNSSEC	⚠️ Not signed
A	157.173.216.245^{🇬🇧 IIHOS001157.173.216.0/21 HOSTINGER IN}
NS	`ns23.domaincontrol.com` ⭐
		A	2603:5:2151::c^{🇺🇸 GODADDY-DNS2603:5:2150::/44}
			PTR	`ns23.domaincontrol.com`
		A	97.74.101.12^{🇺🇸 GODADDY-DNS97.74.100.0/23}
			PTR	`ns23.domaincontrol.com`
NS	`ns24.domaincontrol.com`
		A	2603:5:2251::c^{🇺🇸 GODADDY-DNS2603:5:2250::/44}
			PTR	`ns24.domaincontrol.com`
		A	173.201.69.12^{🇺🇸 GODADDY-DNS173.201.68.0/23}
			PTR	`ns24.domaincontrol.com`
MX	`aspmx.l.google.com` ⭐
		A	2607:f8b0:4004:c23::1a^{🇺🇸 Google2607:f8b0:4004::/48}
			PTR	`yuiadrs-in-f26.1e100.net`
		A	172.253.139.26^{🇺🇸 Google172.253.139.0/24}
			PTR	`yuiadsk-in-f26.1e100.net`
MX	`alt1.aspmx.l.google.com`⁽⁵⁾
		A	2800:3f0:4003:c0f::1a^{🇨🇱 Google2800:3f0:4003::/48}
		A	108.177.123.27^{🇺🇸 Google108.177.123.0/24}
			PTR	`lcscld-in-f27.1e100.net`
MX	`alt2.aspmx.l.google.com`⁽⁵⁾
		A	2a00:1450:400b:c02::1b^{🇮🇪 Google2a00:1450:400b::/48}
			PTR	`dj-in-f27.1e100.net`
		A	172.253.116.27^{🇺🇸 Google172.253.116.0/24}
			PTR	`dj-in-f27.1e100.net`
MX	`alt3.aspmx.l.google.com`⁽¹⁰⁾
		A	2a00:1450:4009:c0f::1a^{🇬🇧 Google2a00:1450:4009::/48}
			PTR	`yulhrs-in-f26.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`
SOA	`ns23.domaincontrol.com`dns@jomax.net 2025-02-21 #5

`com`

	DNSSEC	🔒 Signed (DS record present)
	NS	`a.gtld-servers.net` ⭐
	NS	`b.gtld-servers.net`
	NS	`c.gtld-servers.net`
	NS	`d.gtld-servers.net`
	NS	`e.gtld-servers.net`
	NS	`f.gtld-servers.net`
	NS	`g.gtld-servers.net`
	NS	`h.gtld-servers.net`
	NS	`i.gtld-servers.net`
	NS	`j.gtld-servers.net`
	NS	`k.gtld-servers.net`
	NS	`l.gtld-servers.net`
	NS	`m.gtld-servers.net`
	SOA	`a.gtld-servers.net`nstld@verisign-grs.com serial=1781777005

Previously MX for

indscope.com

Same first word

indscope.com

Similar names

DNS History

17 records (8 active, 9 former)

○NSns1.volkha.com2015-07-12 → 2020-03-13 · 6 obs

● 2015-07-12 01:38:08
○ 2015-11-14 18:48:48
○ 2017-02-08 11:35:20
● 2020-03-13 04:14:32
○ 2026-02-14 19:10:44
○ 2026-06-18 10:10:50

○NSns1.wmirchi.com2015-11-14 → 2017-02-08 · 5 obs

○ 2015-07-12 01:38:08
● 2015-11-14 18:48:48
● 2017-02-08 11:35:20
○ 2020-03-13 04:14:32
○ 2026-06-18 10:10:50

○NSns2.volkha.com2015-07-12 → 2020-03-13 · 6 obs

● 2015-07-12 01:38:08
○ 2015-11-14 18:48:48
○ 2017-02-08 11:35:20
● 2020-03-13 04:14:32
○ 2026-02-14 19:10:44
○ 2026-06-18 10:10:50

○NSns2.wmirchi.com2015-11-14 → 2017-02-08 · 5 obs

○ 2015-07-12 01:38:08
● 2015-11-14 18:48:48
● 2017-02-08 11:35:20
○ 2020-03-13 04:14:32
○ 2026-06-18 10:10:50

●NSns23.domaincontrol.com2026-02-14 → 2026-06-18 · 3 obs

○ 2020-03-13 04:14:32
● 2026-02-14 19:10:44
● 2026-06-18 10:10:50

●NSns24.domaincontrol.com2026-02-14 → 2026-06-18 · 3 obs

○ 2020-03-13 04:14:32
● 2026-02-14 19:10:44
● 2026-06-18 10:10:50

●MXalt1.aspmx.l.google.com2026-02-14 → 2026-06-18 · 3 obs

○ 2020-03-13 04:14:32
● 2026-02-14 19:10:44
● 2026-06-18 10:10:50

●MXalt2.aspmx.l.google.com2026-02-14 → 2026-06-18 · 3 obs

○ 2020-03-13 04:14:32
● 2026-02-14 19:10:44
● 2026-06-18 10:10:50

●MXalt3.aspmx.l.google.com2026-02-14 → 2026-06-18 · 3 obs

○ 2020-03-13 04:14:32
● 2026-02-14 19:10:44
● 2026-06-18 10:10:50

●MXalt4.aspmx.l.google.com2026-02-14 → 2026-06-18 · 3 obs

○ 2020-03-13 04:14:32
● 2026-02-14 19:10:44
● 2026-06-18 10:10:50

●MXaspmx.l.google.com2026-02-14 → 2026-06-18 · 3 obs

○ 2020-03-13 04:14:32
● 2026-02-14 19:10:44
● 2026-06-18 10:10:50

○MXindscope.com2015-07-12 → 2020-03-13 · 4 obs

● 2015-07-12 01:38:08
● 2020-03-13 04:14:32
○ 2026-02-14 19:10:44
○ 2026-06-18 10:10:50

○A137.74.53.1812020-03-13 → 2020-03-13 · 4 obs

○ 2017-02-08 11:35:20
● 2020-03-13 04:14:32
○ 2026-02-14 19:10:44
○ 2026-06-18 10:10:50

●A157.173.216.2452026-02-14 → 2026-06-18 · 3 obs

○ 2020-03-13 04:14:32
● 2026-02-14 19:10:44
● 2026-06-18 10:10:50

○A46.4.68.2282015-07-12 → 2015-07-12 · 3 obs

● 2015-07-12 01:38:08
○ 2015-11-14 18:48:48
○ 2026-06-18 10:10:50

○A5.196.92.1052017-02-08 → 2017-02-08 · 4 obs

○ 2016-06-19 21:56:22
● 2017-02-08 11:35:20
○ 2020-03-13 04:14:32
○ 2026-06-18 10:10:50

○A94.23.33.1312015-11-14 → 2016-06-19 · 5 obs

○ 2015-07-12 01:38:08
● 2015-11-14 18:48:48
● 2016-06-19 21:56:22
○ 2017-02-08 11:35:20
○ 2026-06-18 10:10:50

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	l.gtld-servers.net, j.gtld-servers.net, h.gtld-servers.net, d.gtld-servers.net...	-
indscope.com	ns23.domaincontrol.com, ns24.domaincontrol.com	4 records

✅ Authoritative Response

Server:173.201.69.12

NS records: ns23.domaincontrol.com, ns24.domaincontrol.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for indscope.com (unsigned zone)

⏱️ Timing

Total: 280ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`157.173.216.245`
NS	2	`ns23.domaincontrol.com, ns24.domaincontrol.com`
MX	5	`aspmx.l.google.com (pri: 1), alt1.aspmx.l.google.com (pri: 5)...`
SOA	1	`ns23.domaincontrol.com dns.jomax.net`

📌 Glue Records Collected

Total: 4

Out-of-bailiwick: 4 (ns23.domaincontrol.com, ns23.domaincontrol.com, ns24.domaincontrol.com...)

Analysis

IP Addresses

indscope.com resolves to just one IP address, 157.173.216.245.

Two other host names, along with alpinepublicschool.com, amitnath.in and etsyinfo.com, also share IP numbers with indscope.com.

Name Servers

indscope.com is delegated to two name servers: ns23.domaincontrol.com and ns24.domaincontrol.com.

indscope.com shares its NS records with other domains, for example aloeorganic.org, websitesfornonprofits.org, yardmap.com and two others.

ns23.domaincontrol.com and ns24.domaincontrol.com each resolve to two IP addresses: ns23.domaincontrol.com points to 97.74.101.12 and 2603:5:2151::c, while ns24.domaincontrol.com points to 173.201.69.12 and 2603:5:2251::c.

Mail Servers

Mail for indscope.com is handled by five mail servers, namely aspmx.l.google.com, alt1.aspmx.l.google.com, alt2.aspmx.l.google.com and two others.

There is at least a partial MX overlap between indscope.com and other domains, including ns500699.ns500699.ns500693.ns500699.ns500699.ns500734.ns500693.ns500683.ns500699.ns500693.ns500588.ns500632.ns500632.ns500588.ns500588.ns500588.dtrkdll.com, ns500759.ns500759.ns500759.ns500759.ns500758.ns500735.ns500736.ns500698.ns500698.ns500698.ns500576.ns500698.ns500619.ns500686.ns500619.trackreceptor.com, ns500699.ns500699.ns500693.ns500734.ns500693.ns500734.ns500683.ns500683.ns500683.ns500683.ns500588.ns500632.ns500632.ns500588.ns500588.ns500588.dtrkdll.com and two others.

alt3.aspmx.l.google.com, alt4.aspmx.l.google.com, aspmx2.googlemail.com and aspmx3.googlemail.com are mail servers that frequently appear together with these mail servers.

Host names that have two IP addresses:

aspmx.l.google.com points to 172.253.139.26 and 2607:f8b0:4004:c23::1a.

alt1.aspmx.l.google.com points to 108.177.123.27 and 2800:3f0:4003:c0f::1a.

alt2.aspmx.l.google.com points to 172.253.116.27 and 2a00:1450:400b:c02::1b.

alt3.aspmx.l.google.com points to 192.178.223.26 and 2a00:1450:4009:c0f::1a.

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