flagshipcode.com - dns.ninja

🛡️Domain Reputation CheckBlocklist, phishing & malware status→

`flagshipcode.com`

DNSSEC	⚠️ Not signed
A	35.71.142.77^{🇺🇸 Amazon35.71.128.0/20}
		PTR	`a0b1d980e1f2226c6.awsglobalaccelerator.com`
A	52.223.52.2^{🇺🇸 Amazon52.223.48.0/20}
NS	`dns1.registrar-servers.com` ⭐
		A	2610:a1:1024::200^{🇺🇸 MAINT-ID-120082610:a1:1024::/48 Neustar}
			PTR	`dns1.namecheaphosting.com`
			PTR	`dns1.registrar-servers.com`
		A	156.154.132.200^{🇺🇸 MAINT-ID-12008156.154.132.0/24 Neustar}
			PTR	`dns1.namecheaphosting.com`
			PTR	`dns1.registrar-servers.com`
NS	`dns2.registrar-servers.com`
		A	2610:a1:1025::200^{🇺🇸 MAINT-ID-120082610:a1:1025::/48 Neustar}
			PTR	`dns2.namecheaphosting.com`
			PTR	`dns2.registrar-servers.com`
		A	156.154.133.200^{🇺🇸 MAINT-ID-12008156.154.133.0/24 Neustar}
			PTR	`dns2.namecheaphosting.com`
			PTR	`dns2.registrar-servers.com`
MX	`aspmx.l.google.com` ⭐
		A	2607:f8b0:4023:200d::1a^{🇺🇸 Google2607:f8b0::/32}
			PTR	`yuphxrp-in-f26.1e100.net`
		A	172.217.75.26^{🇺🇸 Google172.217.75.0/24}
			PTR	`yuphxej-in-f26.1e100.net`
MX	`alt1.aspmx.l.google.com`⁽⁵⁾
		A	2607:f8b0:4023:3003::1b^{🇺🇸 Google2607:f8b0::/32}
			PTR	`yulnkjt-in-f27.1e100.net`
		A	172.253.145.27^{🇺🇸 Google172.253.145.0/24}
			PTR	`yulnkjt-in-f27.1e100.net`
MX	`alt2.aspmx.l.google.com`⁽⁵⁾
		A	2607:f8b0:4023:1015::1b^{🇺🇸 Google2607:f8b0::/32}
			PTR	`yudfwta-in-f27.1e100.net`
		A	172.253.135.27^{🇺🇸 Google172.253.135.0/24}
			PTR	`yudfwta-in-f27.1e100.net`
MX	`aspmx2.googlemail.com`⁽¹⁰⁾
		A	2800:3f0:4003:c14::1b^{🇨🇱 Google2800:3f0:4003::/48}
		A	192.178.234.27^{🇺🇸 Google192.178.0.0/15}
			PTR	`ncsclj-in-f27.1e100.net`
MX	`aspmx3.googlemail.com`⁽¹⁰⁾
		A	2607:f8b0:4023:1015::1a^{🇺🇸 Google2607:f8b0::/32}
			PTR	`yudfwta-in-f26.1e100.net`
		A	172.253.135.26^{🇺🇸 Google172.253.135.0/24}
			PTR	`yudfwta-in-f26.1e100.net`
TXT	`google-site-verification=M86ssQPXGea_FRz7SlLpB3Tm-QmWXkyfpaNnqO_6WIQ`
SOA	`dns1.registrar-servers.com`hostmaster@registrar-servers.com serial=1723241275

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

Same first word

flagshipcode.tech

flagshipcode.com

Previous names

Next names

DNS History

17 records (9 active, 8 former)

●NSdns1.registrar-servers.com2026-09-24 → 2026-10-23 · 3 obs

○ 2017-07-03 11:13:36
● 2026-09-24 02:03:02
● 2026-10-23 20:59:52

●NSdns2.registrar-servers.com2026-09-24 → 2026-10-23 · 3 obs

○ 2017-07-03 11:13:36
● 2026-09-24 02:03:02
● 2026-10-23 20:59:52

○NSns1.box.flagshipcode.com2017-07-03 → 2017-07-03 · 4 obs

○ 2016-12-17 06:53:20
● 2017-07-03 11:13:36
○ 2026-09-24 02:03:02
○ 2026-10-23 20:59:52

○NSns1.jones.yodaconditions.com2016-12-17 → 2016-12-17 · 3 obs

● 2016-12-17 06:53:20
○ 2017-07-03 11:13:36
○ 2026-10-23 20:59:52

○NSns2.box.flagshipcode.com2017-07-03 → 2017-07-03 · 4 obs

○ 2016-12-17 06:53:20
● 2017-07-03 11:13:36
○ 2026-09-24 02:03:02
○ 2026-10-23 20:59:52

○NSns2.jones.yodaconditions.com2016-12-17 → 2016-12-17 · 3 obs

● 2016-12-17 06:53:20
○ 2017-07-03 11:13:36
○ 2026-10-23 20:59:52

●MXalt1.aspmx.l.google.com2026-09-24 → 2026-10-23 · 3 obs

○ 2017-07-03 11:13:36
● 2026-09-24 02:03:02
● 2026-10-23 20:59:52

●MXalt2.aspmx.l.google.com2026-09-24 → 2026-10-23 · 3 obs

○ 2017-07-03 11:13:36
● 2026-09-24 02:03:02
● 2026-10-23 20:59:52

●MXaspmx.l.google.com2026-09-24 → 2026-10-23 · 3 obs

○ 2017-07-03 11:13:36
● 2026-09-24 02:03:02
● 2026-10-23 20:59:52

●MXaspmx2.googlemail.com2026-09-24 → 2026-10-23 · 3 obs

○ 2017-07-03 11:13:36
● 2026-09-24 02:03:02
● 2026-10-23 20:59:52

●MXaspmx3.googlemail.com2026-09-24 → 2026-10-23 · 3 obs

○ 2017-07-03 11:13:36
● 2026-09-24 02:03:02
● 2026-10-23 20:59:52

○MXbox.flagshipcode.com2017-07-03 → 2017-07-03 · 4 obs

○ 2016-12-17 06:53:20
● 2017-07-03 11:13:36
○ 2026-09-24 02:03:02
○ 2026-10-23 20:59:52

○MXjones.yodaconditions.com2016-12-17 → 2016-12-17 · 3 obs

● 2016-12-17 06:53:20
○ 2017-07-03 11:13:36
○ 2026-10-23 20:59:52

○A103.11.64.2332016-12-17 → 2016-12-17 · 3 obs

● 2016-12-17 06:53:20
○ 2017-07-03 11:13:36
○ 2026-10-23 20:59:52

○A104.129.43.102017-07-03 → 2017-07-03 · 4 obs

○ 2016-12-17 06:53:20
● 2017-07-03 11:13:36
○ 2026-09-24 02:03:02
○ 2026-10-23 20:59:52

●A35.71.142.772026-09-24 → 2026-10-23 · 3 obs

○ 2017-07-03 11:13:36
● 2026-09-24 02:03:02
● 2026-10-23 20:59:52

●A52.223.52.22026-09-24 → 2026-10-23 · 3 obs

○ 2017-07-03 11:13:36
● 2026-09-24 02:03:02
● 2026-10-23 20:59:52

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	l.gtld-servers.net, j.gtld-servers.net, h.gtld-servers.net, d.gtld-servers.net...	-
flagshipcode.com	dns1.registrar-servers.com, dns2.registrar-servers.com	4 records

✅ Authoritative Response

Server:156.154.132.200

NS records: dns1.registrar-servers.com, dns2.registrar-servers.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for flagshipcode.com (unsigned zone)

⏱️ Timing

Total: 1354ms | Queries: -

📄 Records

Type	Count	Sample Data
A	2	`52.223.52.2, 35.71.142.77`
NS	2	`dns1.registrar-servers.com, dns2.registrar-servers.com`
MX	5	`aspmx.l.google.com (pri: 1), alt1.aspmx.l.google.com (pri: 5)...`
TXT	1	`google-site-verification=M86ssQPXGea_FRz`
SOA	1	`dns1.registrar-servers.com hostmaster.re`

📌 Glue Records Collected

Total: 4

Out-of-bailiwick: 4 (dns1.registrar-servers.com, dns1.registrar-servers.com, dns2.registrar-servers.com...)

Analysis

IP Addresses

flagshipcode.com has two IP addresses: 35.71.142.77 and 52.223.52.2

Two other host names, along with pingaksh.com, quarq.studio and chaldean.international, also share IP numbers with flagshipcode.com.

Name Servers

flagshipcode.com is delegated to two name servers: dns1.registrar-servers.com and dns2.registrar-servers.com.

flagshipcode.com shares its NS records with other domains, for example aumi.co.uk, yatpanel.com, goldseekmines.com and two others.

dns1.registrar-servers.com and dns2.registrar-servers.com each resolve to two IP addresses: dns1.registrar-servers.com points to 156.154.132.200 and 2610:a1:1024::200, while dns2.registrar-servers.com points to 156.154.133.200 and 2610:a1:1025::200.

Mail Servers

Five mail servers handle flagshipcode.com: aspmx2.googlemail.com, aspmx3.googlemail.com, aspmx.l.google.com and two others.

There is at least a partial MX overlap between flagshipcode.com and other domains, including tele-scoop.fr, colporsoft.com, soulfulabode.com and two others.

These mail servers tend to appear in combination with mail servers alt2.aspmx.l.google.com, alt1.aspmx.l.google.com, alt3.aspmx.l.google.com and 3 others.

Host names that have two IP addresses:

aspmx2.googlemail.com points to 192.178.234.27 and 2800:3f0:4003:c14::1b.

aspmx3.googlemail.com points to 172.253.135.26 and 2607:f8b0:4023:1015::1a.

aspmx.l.google.com points to 172.217.75.26 and 2607:f8b0:4023:200d::1a.

alt1.aspmx.l.google.com points to 172.253.145.27 and 2607:f8b0:4023:3003::1b.

alt2.aspmx.l.google.com points to 172.253.135.27 and 2607:f8b0:4023:1015::1b.