fcsecure.com - dns.ninja
fcsecure.com
| DNSSEC | ⚠️ Not signed | ||||||
| NS | dns101.register.com ⭐ | ||||||
| A | 162.159.24.117Cloudflare162.159.24.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US | ||||||
| NS | dns102.register.com | ||||||
| A | 162.159.25.158Cloudflare162.159.25.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US | ||||||
| SOA | DNS101.REGISTER.comroot@REGISTER.com serial=120042815 | ||||||
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.netnstld@verisign-grs.com serial=1784904597 | ||||||
PTR for
Subdomains
server1.fcsecure.com |
Same first word
fcsecure.com |
Similar names
DNS History
18 records (2 active, 16 former)
○NSdns010.d.register.com2020-02-17 → 2020-02-17 · 4 obs
○ 2017-03-26 17:57:00
● 2020-02-17 02:48:22
○ 2026-05-10 13:01:14
○ 2026-07-24 15:09:44
● 2020-02-17 02:48:22
○ 2026-05-10 13:01:14
○ 2026-07-24 15:09:44
○NSdns036.b.register.com2020-02-17 → 2020-02-17 · 4 obs
○ 2017-03-26 17:57:00
● 2020-02-17 02:48:22
○ 2026-05-10 13:01:14
○ 2026-07-24 15:09:44
● 2020-02-17 02:48:22
○ 2026-05-10 13:01:14
○ 2026-07-24 15:09:44
○NSdns037.a.register.com2020-02-17 → 2020-02-17 · 4 obs
○ 2017-03-26 17:57:00
● 2020-02-17 02:48:22
○ 2026-05-10 13:01:14
○ 2026-07-24 15:09:44
● 2020-02-17 02:48:22
○ 2026-05-10 13:01:14
○ 2026-07-24 15:09:44
○NSdns1.registrar-servers.com2015-05-28 → 2016-08-09 · 4 obs
● 2015-05-28 06:32:24
● 2016-08-09 16:45:12
○ 2017-03-26 17:57:00
○ 2026-07-24 15:09:44
● 2016-08-09 16:45:12
○ 2017-03-26 17:57:00
○ 2026-07-24 15:09:44
●NSdns101.register.com2026-05-10 → 2026-07-24 · 3 obs
○ 2020-02-17 02:48:22
● 2026-05-10 13:01:14
● 2026-07-24 15:09:44
● 2026-05-10 13:01:14
● 2026-07-24 15:09:44
●NSdns102.register.com2026-05-10 → 2026-07-24 · 3 obs
○ 2020-02-17 02:48:22
● 2026-05-10 13:01:14
● 2026-07-24 15:09:44
● 2026-05-10 13:01:14
● 2026-07-24 15:09:44
○NSdns153.c.register.com2020-02-17 → 2020-02-17 · 4 obs
○ 2017-03-26 17:57:00
● 2020-02-17 02:48:22
○ 2026-05-10 13:01:14
○ 2026-07-24 15:09:44
● 2020-02-17 02:48:22
○ 2026-05-10 13:01:14
○ 2026-07-24 15:09:44
○NSdns2.registrar-servers.com2015-10-17 → 2016-08-09 · 5 obs
○ 2015-05-28 06:32:24
● 2015-10-17 20:45:28
● 2016-08-09 16:45:12
○ 2017-03-26 17:57:00
○ 2026-07-24 15:09:44
● 2015-10-17 20:45:28
● 2016-08-09 16:45:12
○ 2017-03-26 17:57:00
○ 2026-07-24 15:09:44
○NSdns3.registrar-servers.com2015-10-17 → 2016-08-09 · 5 obs
○ 2015-05-28 06:32:24
● 2015-10-17 20:45:28
● 2016-08-09 16:45:12
○ 2017-03-26 17:57:00
○ 2026-07-24 15:09:44
● 2015-10-17 20:45:28
● 2016-08-09 16:45:12
○ 2017-03-26 17:57:00
○ 2026-07-24 15:09:44
○NSdns4.registrar-servers.com2015-10-17 → 2016-08-09 · 5 obs
○ 2015-05-28 06:32:24
● 2015-10-17 20:45:28
● 2016-08-09 16:45:12
○ 2017-03-26 17:57:00
○ 2026-07-24 15:09:44
● 2015-10-17 20:45:28
● 2016-08-09 16:45:12
○ 2017-03-26 17:57:00
○ 2026-07-24 15:09:44
○NSdns5.registrar-servers.com2015-10-17 → 2016-08-09 · 5 obs
○ 2015-05-28 06:32:24
● 2015-10-17 20:45:28
● 2016-08-09 16:45:12
○ 2017-03-26 17:57:00
○ 2026-07-24 15:09:44
● 2015-10-17 20:45:28
● 2016-08-09 16:45:12
○ 2017-03-26 17:57:00
○ 2026-07-24 15:09:44
○NSns1.uniregistrymarket.link2017-03-26 → 2017-03-26 · 4 obs
○ 2016-08-09 16:45:12
● 2017-03-26 17:57:00
○ 2020-02-17 02:48:22
○ 2026-07-24 15:09:44
● 2017-03-26 17:57:00
○ 2020-02-17 02:48:22
○ 2026-07-24 15:09:44
○NSns2.uniregistrymarket.link2017-03-26 → 2017-03-26 · 4 obs
○ 2016-08-09 16:45:12
● 2017-03-26 17:57:00
○ 2020-02-17 02:48:22
○ 2026-07-24 15:09:44
● 2017-03-26 17:57:00
○ 2020-02-17 02:48:22
○ 2026-07-24 15:09:44
○MXplatelayers.fcsecure.com2015-05-28 → 2016-08-09 · 4 obs
● 2015-05-28 06:32:24
● 2016-08-09 16:45:12
○ 2017-03-26 17:57:00
○ 2026-07-24 15:09:44
● 2016-08-09 16:45:12
○ 2017-03-26 17:57:00
○ 2026-07-24 15:09:44
○MXstupendous.fcsecure.com2015-05-28 → 2016-08-09 · 4 obs
● 2015-05-28 06:32:24
● 2016-08-09 16:45:12
○ 2017-03-26 17:57:00
○ 2026-07-24 15:09:44
● 2016-08-09 16:45:12
○ 2017-03-26 17:57:00
○ 2026-07-24 15:09:44
○A38.84.70.2002015-10-17 → 2016-08-09 · 5 obs
○ 2015-05-28 06:32:24
● 2015-10-17 20:45:28
● 2016-08-09 16:45:12
○ 2017-03-26 17:57:00
○ 2026-07-24 15:09:44
● 2015-10-17 20:45:28
● 2016-08-09 16:45:12
○ 2017-03-26 17:57:00
○ 2026-07-24 15:09:44
○A38.84.70.2312015-05-28 → 2015-05-28 · 3 obs
● 2015-05-28 06:32:24
○ 2015-10-17 20:45:28
○ 2026-07-24 15:09:44
○ 2015-10-17 20:45:28
○ 2026-07-24 15:09:44
○A69.172.201.1532017-03-26 → 2017-03-26 · 4 obs
○ 2016-08-09 16:45:12
● 2017-03-26 17:57:00
○ 2020-02-17 02:48:22
○ 2026-07-24 15:09:44
● 2017-03-26 17:57:00
○ 2020-02-17 02:48:22
○ 2026-07-24 15:09:44
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | j.gtld-servers.net, k.gtld-servers.net, l.gtld-servers.net, m.gtld-servers.net... | - |
| fcsecure.com | dns101.register.com, dns102.register.com | 2 records |
✅ Authoritative Response
Server:162.159.25.158
NS records: dns101.register.com, dns102.register.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for fcsecure.com (unsigned zone)
⏱️ Timing
Total: 167ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| NS | 2 | dns102.register.com, dns101.register.com |
| SOA | 1 | DNS101.REGISTER.com root.REGISTER.com |
📌 Glue Records Collected
Total: 2
Out-of-bailiwick: 2 (dns101.register.com, dns102.register.com)
Analysis
Hierarchy
The domain server1.fcsecure.com falls under the parent fcsecure.com.
Name Servers
The NS records for fcsecure.com delegate to dns101.register.com and dns102.register.com.
fcsecure.com uses the same name servers as several other domains — among them tomtomei.com, eliteghostwriter.net, mobeon.com and two more.
fcsecure.com and other domains like cci.la share at least a portion of their name servers.
Each of dns101.register.com and dns102.register.com has one IP address: dns101.register.com uses 162.159.24.117 and dns102.register.com uses 162.159.25.158.