flagshipcorridor.com - dns.ninja

`flagshipcorridor.com`

DNSSEC	⚠️ Not signed
A	72.251.7.22^{🇨🇦 OVH72.251.0.0/17 Hosting route}
		PTR	`ip22.ip-72-251-7.net`
A	72.251.7.23^{🇨🇦 OVH72.251.0.0/17 Hosting route}
NS	`ns1.lander.d.parity.domains` ⭐ ⚠️ Not in parent delegation
		A	192.236.150.131^{🇺🇸 HOSTWINDS-1192.236.128.0/17 MNT-HL-29 route 192.236.128.000/17 AS54290}
NS	`dns101.registrar-servers.com` ⚠️ Not in zone NS records
		A	192.236.150.131^{🇺🇸 HOSTWINDS-1192.236.128.0/17 MNT-HL-29 route 192.236.128.000/17 AS54290}
NS	`dns102.registrar-servers.com` ⚠️ Not in zone NS records
		A	162.222.205.190^{🇺🇸 IONOS-AS162.222.200.0/21 1&1 Internet Inc. 701 Lee Rd, Suite 300 Chesterbrook, PA 19087 US}
NS	`ns2.lander.d.parity.domains` ⚠️ Not in parent delegation
		A	162.222.205.190^{🇺🇸 IONOS-AS162.222.200.0/21 1&1 Internet Inc. 701 Lee Rd, Suite 300 Chesterbrook, PA 19087 US}
SOA	`ns1.lander.d.parity.domains`hostmaster@lander.d.parity.domains serial=7

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

Previously MX for

flagshipcorridor.com

Same first word

flagshipcorridor.com

DNS History

19 records (6 active, 13 former)

○NSdns1.registrar-servers.com2026-03-18 → 2026-03-18 · 3 obs

○ 2017-05-29 04:13:06
● 2026-03-18 06:26:52
○ 2026-08-01 20:14:58

●NSdns101.registrar-servers.com2026-08-01 → 2026-08-01 · 2 obs

○ 2026-03-18 06:26:52
● 2026-08-01 20:14:58

●NSdns102.registrar-servers.com2026-08-01 → 2026-08-01 · 2 obs

○ 2026-03-18 06:26:52
● 2026-08-01 20:14:58

○NSdns2.registrar-servers.com2026-03-18 → 2026-03-18 · 3 obs

○ 2017-05-29 04:13:06
● 2026-03-18 06:26:52
○ 2026-08-01 20:14:58

●NSns1.lander.d.parity.domains2026-08-01 → 2026-08-01 · 2 obs

○ 2026-03-18 06:26:52
● 2026-08-01 20:14:58

○NSns101.mschosting.com2015-07-23 → 2017-05-29 · 4 obs

● 2015-07-23 01:53:26
● 2017-05-29 04:13:06
○ 2026-03-18 06:26:52
○ 2026-08-01 20:14:58

○NSns102.mschosting.com2015-07-23 → 2017-05-29 · 4 obs

● 2015-07-23 01:53:26
● 2017-05-29 04:13:06
○ 2026-03-18 06:26:52
○ 2026-08-01 20:14:58

●NSns2.lander.d.parity.domains2026-08-01 → 2026-08-01 · 2 obs

○ 2026-03-18 06:26:52
● 2026-08-01 20:14:58

○MXeforward1.registrar-servers.com2026-03-18 → 2026-03-18 · 3 obs

○ 2017-05-29 04:13:06
● 2026-03-18 06:26:52
○ 2026-08-01 20:14:58

○MXeforward2.registrar-servers.com2026-03-18 → 2026-03-18 · 3 obs

○ 2017-05-29 04:13:06
● 2026-03-18 06:26:52
○ 2026-08-01 20:14:58

○MXeforward3.registrar-servers.com2026-03-18 → 2026-03-18 · 3 obs

○ 2017-05-29 04:13:06
● 2026-03-18 06:26:52
○ 2026-08-01 20:14:58

○MXeforward4.registrar-servers.com2026-03-18 → 2026-03-18 · 3 obs

○ 2017-05-29 04:13:06
● 2026-03-18 06:26:52
○ 2026-08-01 20:14:58

○MXeforward5.registrar-servers.com2026-03-18 → 2026-03-18 · 3 obs

○ 2017-05-29 04:13:06
● 2026-03-18 06:26:52
○ 2026-08-01 20:14:58

○MXflagshipcorridor.com2015-07-23 → 2017-05-29 · 4 obs

● 2015-07-23 01:53:26
● 2017-05-29 04:13:06
○ 2026-03-18 06:26:52
○ 2026-08-01 20:14:58

○A103.6.196.142015-07-23 → 2016-02-11 · 4 obs

● 2015-07-23 01:53:26
● 2016-02-11 04:15:34
○ 2016-06-19 16:40:44
○ 2026-08-01 20:14:58

○A110.4.45.1802016-06-19 → 2017-05-29 · 5 obs

○ 2016-02-11 04:15:34
● 2016-06-19 16:40:44
● 2017-05-29 04:13:06
○ 2026-03-18 06:26:52
○ 2026-08-01 20:14:58

○A193.124.185.2042026-03-18 → 2026-03-18 · 3 obs

○ 2017-05-29 04:13:06
● 2026-03-18 06:26:52
○ 2026-08-01 20:14:58

●A72.251.7.222026-08-01 → 2026-08-01 · 2 obs

○ 2026-03-18 06:26:52
● 2026-08-01 20:14:58

●A72.251.7.232026-08-01 → 2026-08-01 · 2 obs

○ 2026-03-18 06:26:52
● 2026-08-01 20:14:58

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	l.gtld-servers.net, a.gtld-servers.net, h.gtld-servers.net, d.gtld-servers.net...	-
flagshipcorridor.com	dns101.registrar-servers.com, dns102.registrar-servers.com	2 records

✅ Authoritative Response

Server:192.236.150.131

NS records: dns101.registrar-servers.com, dns102.registrar-servers.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for flagshipcorridor.com (unsigned zone)

⏱️ Timing

Total: 191ms | Queries: -

📄 Records

Type	Count	Sample Data
A	2	`72.251.7.22, 72.251.7.23`
NS	2	`ns1.lander.d.parity.domains, ns2.lander.d.parity.domains`
SOA	1	`ns1.lander.d.parity.domains hostmaster.l`

📌 Glue Records Collected

Total: 2

Out-of-bailiwick: 2 (dns101.registrar-servers.com, dns102.registrar-servers.com)

Analysis

IP Addresses

flagshipcorridor.com points to the IP addresses 72.251.7.22 and 72.251.7.23

Additional host names — intersales.info, lumarethiqonari.com, weeklysovietwhich.digital and two others — share IP numbers with flagshipcorridor.com.

Name Servers

flagshipcorridor.com has four authoritative name servers: dns101.registrar-servers.com, dns102.registrar-servers.com, ns1.lander.d.parity.domains and ns2.lander.d.parity.domains.

The name servers of flagshipcorridor.com overlap at least partially with those of other domains — among them kindle4138.itashaart.com, kathtube.org, vulkandeluxeklub.com and two more.

Each of the host names dns101.registrar-servers.com, dns102.registrar-servers.com, ns1.lander.d.parity.domains and ns2.lander.d.parity.domains has one IP address: dns101.registrar-servers.com resolves to 192.236.150.131, dns102.registrar-servers.com resolves to 162.222.205.190, ns1.lander.d.parity.domains resolves to 192.236.150.131 and ns2.lander.d.parity.domains resolves to 162.222.205.190.

dns101.registrar-servers.com and ns1.lander.d.parity.domains each have 192.236.150.131 IP addresses.

dns102.registrar-servers.com and ns2.lander.d.parity.domains each have 162.222.205.190 IP addresses.