fcscon.com - dns.ninja

`fcscon.com`

DNSSEC	⚠️ Not signed
NS	`ns1-09.azure-dns.com` ⭐
		A	2603:1061:0:700::9^{🇺🇸 Microsoft2603:1000::/25 MICROSOFT}
			PTR	`ns1-09.azure-dns.com`
		A	13.107.236.9^{🇺🇸 Microsoft13.104.0.0/14 MICROSOFT}
			PTR	`ns1-09.azure-dns.com`
NS	`ns2-09.azure-dns.net`
		A	2620:1ec:8ec:700::9^{🇺🇸 Microsoft2620:1ec::/36 MICROSOFT}
			PTR	`ns2-09.azure-dns.net`
		A	150.171.21.9^{🇺🇸 Microsoft150.171.0.0/16 MICROSOFT}
			PTR	`ns2-09.azure-dns.net`
NS	`ns3-09.azure-dns.org`
		A	2a01:111:4000:700::9^{🇬🇧 Microsoft2a01:111:4000::/36}
			PTR	`ns3-09.azure-dns.org`
		A	204.14.183.9^{🇺🇸 Microsoft204.14.180.0/22}
			PTR	`ns3-09.azure-dns.org`
NS	`ns4-09.azure-dns.info`
		A	2620:1ec:bda:700::9^{🇺🇸 Microsoft2620:1ec::/36 MICROSOFT}
			PTR	`ns4-09.azure-dns.info`
		A	208.84.5.9^{🇺🇸 Microsoft208.84.0.0/21 MICROSOFT}
			PTR	`ns4-09.azure-dns.info`
MX	`smtp.google.com` ⭐
		A	2607:f8b0:4004:c1b::1a^{🇺🇸 Google2607:f8b0:4004::/48}
			PTR	`wv-in-f26.1e100.net`
		A	2607:f8b0:4004:c1b::1b^{🇺🇸 Google2607:f8b0:4004::/48}
			PTR	`wv-in-f27.1e100.net`
		A	2607:f8b0:4004:c1d::1b^{🇺🇸 Google2607:f8b0:4004::/48}
			PTR	`ww-in-f27.1e100.net`
		A	2607:f8b0:4004:c29::1a^{🇺🇸 Google2607:f8b0:4004::/48}
			PTR	`yuiadum-in-f26.1e100.net`
		A	142.251.163.26^{🇺🇸 Google142.251.163.0/24}
			PTR	`wv-in-f26.1e100.net`
		A	142.251.163.27^{🇺🇸 Google142.251.163.0/24}
			PTR	`wv-in-f27.1e100.net`
		A	142.251.167.26^{🇺🇸 Google142.251.167.0/24}
			PTR	`ww-in-f26.1e100.net`
		A	142.251.167.27^{🇺🇸 Google142.251.167.0/24}
			PTR	`ww-in-f27.1e100.net`
		A	173.194.45.27^{🇺🇸 Google173.194.0.0/16}
			PTR	`yuiadum-in-f27.1e100.net`
MX	`alt1.aspmx.l.google.com`⁽⁵⁾
		A	2800:3f0:4003:c0f::1a^{🇨🇱 Google2800:3f0:4003::/48}
		A	108.177.123.26^{🇺🇸 Google108.177.123.0/24}
			PTR	`lcscld-in-f26.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.26^{🇺🇸 Google172.253.116.0/24}
			PTR	`dj-in-f26.1e100.net`
TXT	`v=spf1 include:_spf.google.com ~all`
TXT	`v=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAzJUyxWGNjHpPBbi...`
SOA	`ns1-09.azure-dns.com`azuredns-hostmaster@microsoft.com serial=1

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

Same first word

fcscon.com

Similar names

cnfcos.com

sfconc.com

nocfcs.org

scconf.com

scconf.org

ocncfs.ca

cfscon.com

scconf.s3.amazonaws.com

csconf.org

nfccos.com

nscofc.org

scconf.ir

DNS History

16 records (7 active, 9 former)

●NSns1-09.azure-dns.com2026-02-21 → 2026-06-22 · 3 obs

○ 2017-07-01 19:01:02
● 2026-02-21 15:02:24
● 2026-06-22 02:12:36

○NSns11.domaincontrol.com2015-06-30 → 2017-07-01 · 4 obs

● 2015-06-30 12:47:24
● 2017-07-01 19:01:02
○ 2026-02-21 15:02:24
○ 2026-06-22 02:12:36

○NSns12.domaincontrol.com2015-06-30 → 2017-07-01 · 4 obs

● 2015-06-30 12:47:24
● 2017-07-01 19:01:02
○ 2026-02-21 15:02:24
○ 2026-06-22 02:12:36

●NSns2-09.azure-dns.net2026-02-21 → 2026-06-22 · 3 obs

○ 2017-07-01 19:01:02
● 2026-02-21 15:02:24
● 2026-06-22 02:12:36

●NSns3-09.azure-dns.org2026-02-21 → 2026-06-22 · 3 obs

○ 2017-07-01 19:01:02
● 2026-02-21 15:02:24
● 2026-06-22 02:12:36

●NSns4-09.azure-dns.info2026-02-21 → 2026-06-22 · 3 obs

○ 2017-07-01 19:01:02
● 2026-02-21 15:02:24
● 2026-06-22 02:12:36

●MXalt1.aspmx.l.google.com2015-06-30 → 2026-06-22 · 2 obs

● 2015-06-30 12:47:24
● 2026-06-22 02:12:36

●MXalt2.aspmx.l.google.com2015-06-30 → 2026-06-22 · 2 obs

● 2015-06-30 12:47:24
● 2026-06-22 02:12:36

○MXaspmx.l.google.com2015-06-30 → 2017-07-01 · 4 obs

● 2015-06-30 12:47:24
● 2017-07-01 19:01:02
○ 2026-02-21 15:02:24
○ 2026-06-22 02:12:36

○MXaspmx2.googlemail.com2015-06-30 → 2017-07-01 · 4 obs

● 2015-06-30 12:47:24
● 2017-07-01 19:01:02
○ 2026-02-21 15:02:24
○ 2026-06-22 02:12:36

○MXaspmx3.googlemail.com2015-06-30 → 2017-07-01 · 4 obs

● 2015-06-30 12:47:24
● 2017-07-01 19:01:02
○ 2026-02-21 15:02:24
○ 2026-06-22 02:12:36

○MXaspmx4.googlemail.com2015-06-30 → 2017-07-01 · 4 obs

● 2015-06-30 12:47:24
● 2017-07-01 19:01:02
○ 2026-02-21 15:02:24
○ 2026-06-22 02:12:36

○MXaspmx5.googlemail.com2015-06-30 → 2017-07-01 · 4 obs

● 2015-06-30 12:47:24
● 2017-07-01 19:01:02
○ 2026-02-21 15:02:24
○ 2026-06-22 02:12:36

●MXsmtp.google.com2026-02-21 → 2026-06-22 · 3 obs

○ 2017-07-01 19:01:02
● 2026-02-21 15:02:24
● 2026-06-22 02:12:36

○A50.63.202.542016-11-30 → 2017-07-01 · 5 obs

○ 2016-04-20 13:16:10
● 2016-11-30 02:52:44
● 2017-07-01 19:01:02
○ 2026-02-21 15:02:24
○ 2026-06-22 02:12:36

○A72.167.232.1472015-06-30 → 2016-04-20 · 4 obs

● 2015-06-30 12:47:24
● 2016-04-20 13:16:10
○ 2016-11-30 02:52:44
○ 2026-06-22 02:12:36

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	a.gtld-servers.net, e.gtld-servers.net, h.gtld-servers.net, m.gtld-servers.net...	-
fcscon.com	ns1-09.azure-dns.com, ns2-09.azure-dns.net, ns3-09.azure-dns.org, ns4-09.azure-dns.info	2 records

✅ Authoritative Response

Server:150.171.21.9

NS records: ns1-09.azure-dns.com, ns2-09.azure-dns.net, ns3-09.azure-dns.org, ns4-09.azure-dns.info

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for fcscon.com (unsigned zone)

⏱️ Timing

Total: 742ms | Queries: -

📄 Records

Type	Count	Sample Data
NS	4	`ns1-09.azure-dns.com, ns2-09.azure-dns.net...`
MX	3	`smtp.google.com (pri: 1), alt1.aspmx.l.google.com (pri: 5)...`
TXT	2	`v=spf1 include:_spf.google.com ~all, v=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQ`
SOA	1	`ns1-09.azure-dns.com azuredns-hostmaster`

📌 Glue Records Collected

Total: 2

Out-of-bailiwick: 2 (ns1-09.azure-dns.com, ns1-09.azure-dns.com)

Analysis

Name Servers

The authoritative name servers for fcscon.com are ns1-09.azure-dns.com, ns4-09.azure-dns.info, ns2-09.azure-dns.net and ns3-09.azure-dns.org.

The name servers of fcscon.com overlap at least partially with those of other domains — among them 166.52.in-addr.arpa, realbutextraordinary.com, mmaid.jp and two more.

Each of the four hosts ns1-09.azure-dns.com, ns4-09.azure-dns.info, ns2-09.azure-dns.net and ns3-09.azure-dns.org has two IP addresses. ns1-09.azure-dns.com points to 13.107.236.9 and 2603:1061:0:700::9. ns4-09.azure-dns.info points to 208.84.5.9 and 2620:1ec:bda:700::9. ns2-09.azure-dns.net points to 150.171.21.9 and 2620:1ec:8ec:700::9. ns3-09.azure-dns.org points to 204.14.183.9 and 2a01:111:4000:700::9.

Mail Servers

Mail for fcscon.com is routed through three mail servers — smtp.google.com, alt1.aspmx.l.google.com and alt2.aspmx.l.google.com.

fcscon.com has at least partial mail server overlap with other domains such as magnificent.technology, dbd.global, waveguard.com and two more.

These mail servers commonly co-occur with mail servers aspmx.l.google.com, alt4.aspmx.l.google.com, alt3.aspmx.l.google.com and 4 others.

Hostnames that resolve to 9 IP addresses:

smtp.google.com has IP addresses 142.251.163.26, 142.251.163.27 and 142.251.167.26, plus 6 other.

Hostnames that resolve to two IP addresses:

alt1.aspmx.l.google.com has two IP addresses: 108.177.123.26 and 2800:3f0:4003:c0f::1a.

alt2.aspmx.l.google.com has two IP addresses: 172.253.116.26 and 2a00:1450:400b:c02::1b.