fbtrcsc.com
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
Online · 200SafeSSL: 126 days left12 years old
75
fbtrcsc.com was registered on 23 Jan 2014 via GoDaddy.com, LLC and the registry expiry is 23 Jan 2027. WHOIS data came from RDAP at https://rdap.verisign.com/com/v1/domain/fbtrcsc.com.
fbtrcsc.com publishes 2 nameservers. DNSSEC is not signed.
fbtrcsc.com has 1 IPv4 address (13.65.95.109). The geolocation database places 13.65.95.109 in San Antonio, United States.
The TLS certificate from Go Daddy Secure Certificate Authority - G2 is valid and has 126 days left (TLS 1.3). The homepage answered HTTP 200.
Tech detection named Azure, Bootstrap, IIS, Microsoft ASP.NET, Windows Server and jQuery. The fingerprints ran on the homepage that was already downloaded.
No safety warning was recorded for fbtrcsc.com in the checks that ran.
Domain · RDAP/WHOIS
fbtrcsc.com was registered on 23 Jan 2014 via GoDaddy.com, LLC. The registry returned 4 status values and 2 nameservers from https://rdap.verisign.com/com/v1/domain/fbtrcsc.com.
| Registered | since 23 Jan 2014 |
|---|---|
| Created | 23 January 2014 |
| Updated | 24 January 2026 |
| Expires | 23 January 2027 |
| Registrar | GoDaddy.com, LLC |
| Status | client delete prohibited, client renew prohibited, client transfer prohibited, client update prohibited |
| Nameservers | ns07.domaincontrol.com, ns08.domaincontrol.com |
| DNSSEC | no |
| Source | https://rdap.verisign.com/com/v1/domain/fbtrcsc.com |
fbtrcsc.com carries the status "client delete prohibited". The registrar has asked the registry to refuse a delete. This is an EPP status on the domain object. It does not say the website is safe, and it does not name the person who registered it.
fbtrcsc.com carries the status "client renew prohibited". The registrar has asked the registry to refuse a renewal. The expiry date still stands until a different status is set.
fbtrcsc.com carries the status "client transfer prohibited". The registrar has asked the registry to refuse a transfer to another registrar. The status is a lock on the domain object. It is not evidence about the content of the site.
fbtrcsc.com carries the status "client update prohibited". The registrar has asked the registry to refuse updates to the domain object. Contact and nameserver changes wait until the lock is lifted by the registrar of record.
Nameserver ns07.domaincontrol.com is published for fbtrcsc.com in the registration record from https://rdap.verisign.com/com/v1/domain/fbtrcsc.com.
Nameserver ns08.domaincontrol.com is published for fbtrcsc.com in the registration record from https://rdap.verisign.com/com/v1/domain/fbtrcsc.com.
DNS
fbtrcsc.com has 1 address record, 1 mail exchanger and 2 nameservers, measured at 1.1.1.1:53.
| A | 13.65.95.109 |
|---|---|
| AAAA | — |
| NS | ns07.domaincontrol.com, ns08.domaincontrol.com |
| MX | fbtrcsc-com.mail.protection.outlook.com (0) Microsoft 365 |
| SPF | present |
| DMARC | absent |
| CAA | — |
| Wildcard | off |
| DNSSEC | not signed |
| Resolver | 1.1.1.1:53 |
The SPF text record at fbtrcsc.com is "v=spf1 include:spf.protection.outlook.com -all".
IPv4 address 13.65.95.109 answers for fbtrcsc.com at resolver 1.1.1.1:53.
Mail exchanger fbtrcsc-com.mail.protection.outlook.com has preference 0. The host is recognised as Microsoft 365.
Hosting and geo
fbtrcsc.com is placed in San Antonio, United States by the local geolocation database (db-ip).
| Address | 13.65.95.109 |
|---|---|
| Country | United States |
| City | San Antonio |
| Source | db-ip |
SSL/TLS
The certificate for fbtrcsc.com is valid, with 126 days left and 2 subject alternative names. Source: tls:443.
| Issuer | Go Daddy Secure Certificate Authority - G2 |
|---|---|
| Subject | www.fbtrcsc.com |
| Valid from | 3 February 2026 |
| Valid until | 7 March 2027 |
| Days left | 126 |
| SAN count | 2 |
| Protocol | TLS 1.3 |
| Source | tls:443 |
Subject alternative names: fbtrcsc.com, www.fbtrcsc.com.
Tech stack
Tech detection checked the fetched homepage and named 6 products. Source: wappalyzergo.
- Azure · PaaS
- Bootstrap · UI frameworks
- IIS · Web servers
- Microsoft ASP.NET · Web frameworks
- Windows Server · Operating systems
- jQuery · JavaScript libraries
Azure is filed under PaaS.
Bootstrap is filed under UI frameworks.
IIS is filed under Web servers.
Microsoft ASP.NET is filed under Web frameworks.
Windows Server is filed under Operating systems.
jQuery is filed under JavaScript libraries.
On-page checks
The homepage returned HTTP 200 in 130 ms. The target title is 6 characters and the page has 0 H1 headings.
| Status | 200 |
|---|---|
| TTFB | 130 ms |
| Title length | 6 yes |
| Quoted title | "FBCTRA" |
| Meta description | none no |
| H1 count | 0 |
| HSTS | no no |
| CSP | no |
| X-Frame-Options | SAMEORIGIN |
| Robots meta | — |
| Canonical | — |
| Language | — |
| Links | 0 |
| Images | 0 |
| Favicon | yes |
The quoted title and meta description are measurements of the other site. They are not this page's title or description.
Security
Family DNS for fbtrcsc.com is clear, and URLhaus is clear. Source: family DNS and local lists.
| Family DNS | clear |
|---|---|
| URLhaus | clear |
| UT1 | — |
| Web Risk | not run |
| Source | family DNS and local lists |
| HSTS | no |
| CSP | no |
Google Web Risk did not run. No API key is configured, and this report does not invent a clean result from that service.
Score breakdown
Availability 25 of 25. DNS answer plus a homepage status in the 2xx or 3xx range.
TLS 20 of 20. A valid certificate, with extra points when it has at least 14 days left.
DNS hygiene 5 of 20. SPF, DMARC, CAA, and DNSSEC are five points each.
Security headers 5 of 15. HSTS, CSP, and X-Frame-Options or CSP frame-ancestors.
Safety lists 15 of 15. Points only when the checks ran and came back clean. Unknown is not clean.
Domain age 5 of 5. Five points at one year, two points at 30 days.
Change history
- October 2026: geo city changed from empty to San Antonio.
- October 2026: geo country changed from empty to United States.
Questions
Is fbtrcsc.com safe?
The checks that ran did not produce a safety warning, and a score is not a promise that the site is safe.
Who hosts fbtrcsc.com?
fbtrcsc.com is placed in San Antonio, United States.
When does fbtrcsc.com expire?
fbtrcsc.com expires on 23 January 2027 according to https://rdap.verisign.com/com/v1/domain/fbtrcsc.com.
Who owns fbtrcsc.com?
The registry did not return a person or a company for fbtrcsc.com. RDAP often redacts the registrant. The registrar on file is GoDaddy.com, LLC.
Sources
- RDAP source https://rdap.verisign.com/com/v1/domain/fbtrcsc.com at 2026-10-30T13:54:14Z
- DNS source 1.1.1.1:53 at 2026-10-30T13:54:14Z
- TLS source tls:443 at 2026-10-30T13:54:14Z
- HTTP source https://fbtrcsc.com/ at 2026-10-30T13:54:14Z
- Tech source wappalyzergo at 2026-10-30T13:54:14Z
- Geo source db-ip at 2026-10-30T13:54:14Z
- Safety source family DNS and local lists at 2026-10-30T13:54:14Z
Related reports
No other indexable reports share this TLD, host, or registrar yet.
Owner of this site?
Ask for a correction or for the report to be removed from search. Public DNS facts stay on the page. An optional badge is not inserted for you.
How to read this report
The sentences under each heading are filled from the latest snapshot. If a collector had nothing to say, that sentence is left out. The target site's own title and meta description, when shown, are quoted as measurements. They are not this page's title. Change history only lists a difference between two snapshots, so the first check starts the clock and later edits are the history. A malware blocklist is the only reason the homepage body is skipped. That fact stays on the report. It does not by itself drop the page from the sitemap or from related-report links.