`futurepathways.in`

DNSSEC	⚠️ Not signed
A	148.72.52.201^{🇺🇸 AS398101148.72.48.0/21}
		PTR	`201.52.72.148.host.secureserver.net`
NS	`ns17.domaincontrol.com` ⭐
		A	2603:5:21c0::9^{🇺🇸 GODADDY-DNS2603:5:21c0::/44}
			PTR	`ns17.domaincontrol.com`
		A	97.74.108.9^{🇺🇸 GODADDY-DNS97.74.108.0/23}
			PTR	`ns17.domaincontrol.com`
NS	`ns18.domaincontrol.com`
		A	2603:5:22c0::9^{🇺🇸 GODADDY-DNS2603:5:22c0::/44}
			PTR	`ns18.domaincontrol.com`
		A	173.201.76.9^{🇺🇸 GODADDY-DNS173.201.76.0/23}
			PTR	`ns18.domaincontrol.com`
MX	`futurepathways-in.mail.protection.outlook.com` ⭐
		A	2a01:111:f403:cc2c::^{🇮🇳 Microsoft2a01:111:f000::/36}
			PTR	`mail-ma0pr01cu01000.inbound.protection.outlook.com`
		A	2a01:111:f403:cc2c::1^{🇮🇳 Microsoft2a01:111:f000::/36}
			PTR	`mail-ma0pr01cu01101.inbound.protection.outlook.com`
		A	2a01:111:f403:cc2d::^{🇮🇳 Microsoft2a01:111:f000::/36}
			PTR	`mail-pnzpr01cu00200.inbound.protection.outlook.com`
		A	2a01:111:f403:cc2d::1^{🇮🇳 Microsoft2a01:111:f000::/36}
			PTR	`mail-pnypr01cu00201.inbound.protection.outlook.com`
		A	52.101.144.0^{🇮🇳 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-ma0pr01cu01000.inbound.protection.outlook.com`
		A	52.101.144.3^{🇮🇳 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-ma0pr01cu01103.inbound.protection.outlook.com`
		A	52.101.145.0^{🇮🇳 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-pnzpr01cu00200.inbound.protection.outlook.com`
		A	52.101.145.2^{🇮🇳 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-pnypr01cu00202.inbound.protection.outlook.com`
TXT	`v=spf1 include:spf.protection.outlook.com -all`
SOA	`ns17.domaincontrol.com`dns@jomax.net 2022-12-11 #1

`in`

	DNSSEC	🔒 Signed (DS record present)
	NS	`ns01.trs-dns.com` ⭐
	NS	`ns.trs-dns.com`
	NS	`ns01.trs-dns.net`
	NS	`ns10.trs-dns.info`
	NS	`ns10.trs-dns.org`
	SOA	`ns.trs-dns.com`trs-ops@tucows.com serial=1774505523

Previously MX for

futurepathways.in

Same first word

futurepathways.com

futurepathways.in

DNS History

18 records (4 active, 14 former)

○NScass.ns.cloudflare.com2017-06-27 → 2017-06-27 · 4 obs

○ 2016-12-05 23:46:02
● 2017-06-27 02:14:04
○ 2026-03-04 05:09:16
○ 2026-03-26 06:44:16

○NSdane.ns.cloudflare.com2017-06-27 → 2017-06-27 · 4 obs

○ 2016-12-05 23:46:02
● 2017-06-27 02:14:04
○ 2026-03-04 05:09:16
○ 2026-03-26 06:44:16

○NSdns11.parkpage.foundationapi.com2016-12-05 → 2016-12-05 · 4 obs

○ 2016-04-29 03:02:46
● 2016-12-05 23:46:02
○ 2017-06-27 02:14:04
○ 2026-03-26 06:44:16

○NSdns12.parkpage.foundationapi.com2016-12-05 → 2016-12-05 · 4 obs

○ 2016-04-29 03:02:46
● 2016-12-05 23:46:02
○ 2017-06-27 02:14:04
○ 2026-03-26 06:44:16

○NSns1.txldomain.com2016-02-03 → 2016-04-29 · 4 obs

● 2016-02-03 16:06:12
● 2016-04-29 03:02:46
○ 2016-12-05 23:46:02
○ 2026-03-26 06:44:16

●NSns17.domaincontrol.com2026-03-04 → 2026-03-26 · 3 obs

○ 2017-06-27 02:14:04
● 2026-03-04 05:09:16
● 2026-03-26 06:44:16

●NSns18.domaincontrol.com2026-03-04 → 2026-03-26 · 3 obs

○ 2017-06-27 02:14:04
● 2026-03-04 05:09:16
● 2026-03-26 06:44:16

○NSns2.txldomain.com2016-02-03 → 2016-04-29 · 4 obs

● 2016-02-03 16:06:12
● 2016-04-29 03:02:46
○ 2016-12-05 23:46:02
○ 2026-03-26 06:44:16

●MXfuturepathways-in.mail.protection.outlook.com2026-03-04 → 2026-03-26 · 3 obs

○ 2016-12-05 23:46:02
● 2026-03-04 05:09:16
● 2026-03-26 06:44:16

○MXfuturepathways.in2016-02-03 → 2016-04-29 · 4 obs

● 2016-02-03 16:06:12
● 2016-04-29 03:02:46
○ 2016-12-05 23:46:02
○ 2026-03-26 06:44:16

○A104.27.156.112017-06-27 → 2017-06-27 · 4 obs

○ 2016-12-05 23:46:02
● 2017-06-27 02:14:04
○ 2026-03-04 05:09:16
○ 2026-03-26 06:44:16

○A104.27.157.112017-06-27 → 2017-06-27 · 4 obs

○ 2016-12-05 23:46:02
● 2017-06-27 02:14:04
○ 2026-03-04 05:09:16
○ 2026-03-26 06:44:16

●A148.72.52.2012026-03-04 → 2026-03-26 · 3 obs

○ 2017-06-27 02:14:04
● 2026-03-04 05:09:16
● 2026-03-26 06:44:16

○A209.99.40.2232016-12-05 → 2016-12-05 · 4 obs

○ 2016-04-29 03:02:46
● 2016-12-05 23:46:02
○ 2017-06-27 02:14:04
○ 2026-03-26 06:44:16

○A2400:cb00:2048:1::681b:9c0b2017-06-27 → 2017-06-27 · 4 obs

○ 2016-12-05 23:46:02
● 2017-06-27 02:14:04
○ 2026-03-04 05:09:16
○ 2026-03-26 06:44:16

○A2400:cb00:2048:1::681b:9d0b2017-06-27 → 2017-06-27 · 4 obs

○ 2016-12-05 23:46:02
● 2017-06-27 02:14:04
○ 2026-03-04 05:09:16
○ 2026-03-26 06:44:16

○A74.119.146.1722016-02-03 → 2016-04-29 · 4 obs

● 2016-02-03 16:06:12
● 2016-04-29 03:02:46
○ 2016-12-05 23:46:02
○ 2026-03-26 06:44:16

○PTRdns11.parkpage.foundationapi.com2016-12-05 → 2016-12-05 · 3 obs

● 2016-12-05 23:46:02
○ 2017-06-27 02:14:04
○ 2026-03-26 06:44:16

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
in	ns01.trs-dns.com, ns01.trs-dns.net, ns10.trs-dns.org, ns10.trs-dns.info	-
futurepathways.in	ns17.domaincontrol.com, ns18.domaincontrol.com	-

✅ Authoritative Response

Server:173.201.76.9

NS records: ns17.domaincontrol.com, ns18.domaincontrol.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for futurepathways.in (unsigned zone)

⏱️ Timing

Total: 463ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`148.72.52.201`
NS	2	`ns17.domaincontrol.com, ns18.domaincontrol.com`
MX	1	`futurepathways-in.mail.protection.outloo`
TXT	1	`v=spf1 include:spf.protection.outlook.co`
SOA	1	`ns17.domaincontrol.com dns.jomax.net`

Analysis

IP Addresses

futurepathways.in resolves to a single IP address: 148.72.52.201.

Name Servers

futurepathways.in's delegation uses two name servers, ns17.domaincontrol.com and ns18.domaincontrol.com.

futurepathways.in shares the same name server setup as other domains, for example wanderlust-japan.com, myphoto.market, fairwaymfg.net, ocetacea.net and breslevnews.com.

Host names with two IPs:

ns17.domaincontrol.com points to: 2603:5:21c0::9 and 97.74.108.9

ns18.domaincontrol.com points to: 2603:5:22c0::9 and 173.201.76.9

Mail Servers

futurepathways.in is handled by a single mail server, futurepathways-in.mail.protection.outlook.com.

Hostname futurepathways-in.mail.protection.outlook.com points to eight IP numbers: 2a01:111:f403:cc2c::, 2a01:111:f403:cc2c::1, 2a01:111:f403:cc2d::, 2a01:111:f403:cc2d::1, 52.101.144.0, 52.101.144.3, 52.101.145.0 and 52.101.145.2.

futurepathways.in - robtex.com