fcrs.com - dns.ninja
fcrs.com
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=1786771749 | ||||||
Same first word
fcrs.in |
fcrs.de |
fcrs.net |
fcrs.cn |
fcrs.co.za |
fcrs.org.uk |
fcrs.ru |
fcrs.edu.br |
fcrs.ie |
fcrs.org |
fcrs.com |
fcrs.com.au |
Similar names
DNS History
9 records (6 active, 3 former)
●NSdns1.name-services.com2015-08-06 → 2026-08-15 · 2 obs
● 2026-08-15 05:56:26
●NSdns2.name-services.com2015-08-06 → 2026-08-15 · 2 obs
● 2026-08-15 05:56:26
●NSdns3.name-services.com2015-08-06 → 2026-08-15 · 2 obs
● 2026-08-15 05:56:26
●NSdns4.name-services.com2015-08-06 → 2026-08-15 · 2 obs
● 2026-08-15 05:56:26
●NSdns5.name-services.com2015-08-06 → 2026-08-15 · 2 obs
● 2026-08-15 05:56:26
●A64.98.135.1182026-02-18 → 2026-08-15 · 3 obs
● 2026-02-18 23:09:28
● 2026-08-15 05:56:26
○A98.124.198.12015-08-06 → 2015-08-06 · 3 obs
○ 2017-06-27 10:11:24
○ 2026-08-15 05:56:26
○A98.124.199.12015-08-06 → 2015-11-03 · 4 obs
● 2015-11-03 09:44:14
○ 2016-01-24 15:04:24
○ 2026-08-15 05:56:26
○A98.124.199.1182016-01-24 → 2021-11-12 · 5 obs
● 2016-01-24 15:04:24
● 2021-11-12 09:14:10
○ 2026-02-18 23:09:28
○ 2026-08-15 05:56:26
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | h.gtld-servers.net, e.gtld-servers.net, i.gtld-servers.net, k.gtld-servers.net... | - |
| fcrs.com | dns1.name-services.com, dns2.name-services.com, dns3.name-services.com, dns4.name-services.com... | 10 records |
✅ Authoritative Response
Server:216.40.47.201
NS records: dns1.name-services.com, dns2.name-services.com, dns3.name-services.com, dns4.name-services.com, dns5.name-services.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for fcrs.com (unsigned zone)
⏱️ Timing
Total: 315ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 64.98.135.118 |
| NS | 5 | dns5.name-services.com, dns4.name-services.com... |
| SOA | 1 | dns1.name-services.com info.name-service |
📌 Glue Records Collected
Total: 10
Out-of-bailiwick: 10 (dns1.name-services.com, dns1.name-services.com, dns2.name-services.com...)
Analysis
IP Addresses
fcrs.com resolves to just one IP address, 64.98.135.118.
Two other host names, along with andyevancohen.com, mykomen.org and pica(0x706f726e).com, also share IP numbers with fcrs.com.
Name Servers
fcrs.com delegates to five name servers: dns1.name-services.com, dns2.name-services.com, dns3.name-services.com and two others.
At least some of fcrs.com's name servers are shared with other domains, for example wechatspanish.com, dvhsbandboosters.com, lynngroup.com and two more.
These name servers tend to be deployed in combination with the name servers dns4.name-services.com and dns5.name-services.com.
Host names that have two IP addresses:
dns1.name-services.com directs traffic to 64.98.148.137 and 2604:4000:2800:2000:64:98:148:137.
dns2.name-services.com directs traffic to 216.40.47.201 and 2604:4000:0:d:216:40:47:201.
dns3.name-services.com directs traffic to 64.98.148.138 and 2604:4000:2800:2000:64:98:148:138.
dns4.name-services.com directs traffic to 216.40.47.202 and 2604:4000:0:d:216:40:47:202.
dns5.name-services.com directs traffic to 64.98.148.139 and 2604:4000:2800:2000:64:98:148:139.