`fci-dc.com`

DNSSEC	⚠️ Not signed
A	209.137.133.7^{🇺🇸 ASN-KDDA209.137.133.0/24 Ajinomoto Internet RouteNew York CustomersAjinomoto Internet Route}
		PTR	`7.primeconduit.com`
NS	`ns000.d-53.net` ⭐
NS	`ns016-lpvzcrpzvhvd6wxr.l.d-53.info`
		A	2001:240:bb81::28:47^{🇯🇵 IIJ-AS2001:240::/32 IIJ IPv6 BLOCK ( AS2497 )}
			PTR	`s016.d-53.biz`
		A	202.32.219.47^{🇯🇵 IIJ-AS202.32.0.0/16 IIJ IPv4 BLOCK ( AS2497 )}
			PTR	`s016.d-53.biz`
NS	`ns016-lpvzcrpzvhvd6wxr.l.d-53.jp`
		A	2001:240:bb81::29:1107^{🇯🇵 IIJ-AS2001:240::/32 IIJ IPv6 BLOCK ( AS2497 )}
			PTR	`s016.d-53.org`
		A	203.180.146.107^{🇯🇵 IIJ-AS203.180.0.0/16 IIJ IPv4 BLOCK ( AS2497 )}
			PTR	`s016.d-53.org`
NS	`ns016-lpvzcrpzvhvd6wxr.l.d-53.org`
		A	2001:240:bb81::29:107^{🇯🇵 IIJ-AS2001:240::/32 IIJ IPv6 BLOCK ( AS2497 )}
			PTR	`s016.d-53.net`
		A	210.138.20.107^{🇯🇵 IIJ-AS210.138.0.0/16 IIJ IPv4 BLOCK ( AS2497 )}
			PTR	`s016.d-53.net`
MX	`fcidc-com0i.mail.protection.outlook.com` ⭐
		A	2a01:111:f403:c92c::1^{🇺🇸 Microsoft2a01:111:f000::/36}
			PTR	`mail-dm6pr03cu00401.inbound.protection.outlook.com`
		A	2a01:111:f403:c931::1^{🇺🇸 Microsoft2a01:111:f000::/36}
			PTR	`mail-sa9pr03cu00201.inbound.protection.outlook.com`
		A	2a01:111:f403:c946::1^{🇺🇸 Microsoft2a01:111:f000::/36}
			PTR	`mail-ch1pr04cu00101.inbound.protection.outlook.com`
		A	2a01:111:f403:f90d::1^{🇺🇸 Microsoft2a01:111:f000::/36}
			PTR	`mail-sn1pr0501cu00301.inbound.protection.outlook.com`
		A	40.93.192.1^{🇺🇸 Microsoft40.80.0.0/12}
			PTR	`mail-dm5pr02cu00201.inbound.protection.outlook.com`
		A	52.101.9.26^{🇺🇸 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-bl0pr02cu00702.inbound.protection.outlook.com`
		A	52.101.10.5^{🇺🇸 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-bn6pr04cu00105.inbound.protection.outlook.com`
		A	52.101.41.26^{🇺🇸 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-sj0pr03cu01702.inbound.protection.outlook.com`
TXT	`MS=ms62507167`
TXT	`v=spf1 include:spf.protection.outlook.com ~all`
SOA	`ns000.d-53.net`dns-managers@iij.ad.jp serial=132

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

Subdomains

www.fci-dc.com

Same first word

fci-dc.com

Similar names

cdf-ic.com

fcc-id.org

fcc-id.com

DNS History

12 records (6 active, 6 former)

○NSns0.syscomusa.com2015-07-19 → 2018-04-24 · 4 obs

● 2015-07-19 09:44:22
● 2018-04-24 08:05:56
○ 2026-03-11 22:30:42
○ 2026-03-24 11:59:52

●NSns000.d-53.net2026-03-11 → 2026-03-24 · 3 obs

○ 2018-04-24 08:05:56
● 2026-03-11 22:30:42
● 2026-03-24 11:59:52

●NSns016-lpvzcrpzvhvd6wxr.l.d-53.info2026-03-11 → 2026-03-24 · 3 obs

○ 2018-04-24 08:05:56
● 2026-03-11 22:30:42
● 2026-03-24 11:59:52

●NSns016-lpvzcrpzvhvd6wxr.l.d-53.jp2026-03-11 → 2026-03-24 · 3 obs

○ 2018-04-24 08:05:56
● 2026-03-11 22:30:42
● 2026-03-24 11:59:52

●NSns016-lpvzcrpzvhvd6wxr.l.d-53.org2026-03-11 → 2026-03-24 · 3 obs

○ 2018-04-24 08:05:56
● 2026-03-11 22:30:42
● 2026-03-24 11:59:52

○NSns1.syscomusa.com2015-07-19 → 2018-04-24 · 4 obs

● 2015-07-19 09:44:22
● 2018-04-24 08:05:56
○ 2026-03-11 22:30:42
○ 2026-03-24 11:59:52

○MXbmta01.syscomusa.com2017-01-06 → 2018-04-24 · 5 obs

○ 2016-12-26 16:55:00
● 2017-01-06 18:17:54
● 2018-04-24 08:05:56
○ 2026-03-11 22:30:42
○ 2026-03-24 11:59:52

○MXbmta02.syscomusa.com2017-01-06 → 2018-04-24 · 5 obs

○ 2016-12-26 16:55:00
● 2017-01-06 18:17:54
● 2018-04-24 08:05:56
○ 2026-03-11 22:30:42
○ 2026-03-24 11:59:52

○MXfci-dc.com.inbound10.mxlogic.net2015-07-19 → 2016-12-26 · 4 obs

● 2015-07-19 09:44:22
● 2016-12-26 16:55:00
○ 2017-01-06 18:17:54
○ 2026-03-24 11:59:52

○MXfci-dc.com.inbound10.mxlogicmx.net2015-07-19 → 2016-12-26 · 4 obs

● 2015-07-19 09:44:22
● 2016-12-26 16:55:00
○ 2017-01-06 18:17:54
○ 2026-03-24 11:59:52

●MXfcidc-com0i.mail.protection.outlook.com2026-03-11 → 2026-03-24 · 3 obs

○ 2018-04-24 08:05:56
● 2026-03-11 22:30:42
● 2026-03-24 11:59:52

●A209.137.133.72015-07-19 → 2026-03-24 · 2 obs

● 2015-07-19 09:44:22
● 2026-03-24 11:59:52

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net...	-
fci-dc.com	ns016-lpvzcrpzvhvd6wxr.l.d-53.jp, ns016-lpvzcrpzvhvd6wxr.l.d-53.org, ns016-lpvzcrpzvhvd6wxr.l.d-53.info	-

✅ Authoritative Response

Server:202.32.219.47

NS records: ns016-lpvzcrpzvhvd6wxr.l.d-53.jp, ns016-lpvzcrpzvhvd6wxr.l.d-53.org, ns016-lpvzcrpzvhvd6wxr.l.d-53.info

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for fci-dc.com (unsigned zone)

⏱️ Timing

Total: 996ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`209.137.133.7`
NS	3	`ns016-lpvzcrpzvhvd6wxr.l.d-53.org, ns016-lpvzcrpzvhvd6wxr.l.d-53.info...`
MX	1	`fcidc-com0i.mail.protection.outlook.com`
TXT	2	`MS=ms62507167, v=spf1 include:spf.protection.outlook.co`
SOA	1	`ns000.d-53.net dns-managers.iij.ad.jp`

Analysis

Hierarchy

fci-dc.com is the parent of www.fci-dc.com.

IP Addresses

fci-dc.com resolves to a single IP address: 209.137.133.7.

Other host names, for instance www.fci-dc.com, share IP numbers with fci-dc.com.

Name Servers

fci-dc.com is delegated to four name servers: ns000.d-53.net, ns016-lpvzcrpzvhvd6wxr.l.d-53.info, ns016-lpvzcrpzvhvd6wxr.l.d-53.jp and ns016-lpvzcrpzvhvd6wxr.l.d-53.org.

fci-dc.com at least partially shares name servers with other domains, including shiseido.sk, 185.31.150.in-addr.arpa, ndk.com, hokentsuhan.jp and cfsc.jp.