finceptor.app
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
Online · 200SafeSSL: 40 days left3 years old
80
finceptor.app was registered on 27 Apr 2023 via GoDaddy.com, LLC and the registry expiry is 27 Apr 2028. WHOIS data came from RDAP at https://pubapi.registry.google/rdap/domain/finceptor.app.
finceptor.app publishes 2 nameservers. DNSSEC is not signed.
finceptor.app has 2 IPv4 addresses (188.114.96.3, 188.114.97.3) and 2 IPv6 addresses (2a06:98c1:3120::3, 2a06:98c1:3121::3). The geolocation database places 188.114.96.3 in Toronto, Canada.
The TLS certificate from WE1 is valid and has 40 days left (TLS 1.3). The homepage answered HTTP 200.
Tech detection named Cloudflare, HSTS, HTTP/3 and Vercel. The fingerprints ran on the homepage that was already downloaded.
No safety warning was recorded for finceptor.app in the checks that ran.
Domain · RDAP/WHOIS
finceptor.app was registered on 27 Apr 2023 via GoDaddy.com, LLC. The registry returned 4 status values and 2 nameservers from https://pubapi.registry.google/rdap/domain/finceptor.app.
| Registered | since 27 Apr 2023 |
|---|---|
| Created | 27 April 2023 |
| Updated | 10 October 2025 |
| Expires | 27 April 2028 |
| Registrar | GoDaddy.com, LLC |
| Status | client delete prohibited, client renew prohibited, client transfer prohibited, client update prohibited |
| Nameservers | bristol.ns.cloudflare.com, wells.ns.cloudflare.com |
| DNSSEC | no |
| Source | https://pubapi.registry.google/rdap/domain/finceptor.app |
finceptor.app 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.
finceptor.app 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.
finceptor.app 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.
finceptor.app 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 bristol.ns.cloudflare.com is published for finceptor.app in the registration record from https://pubapi.registry.google/rdap/domain/finceptor.app.
Nameserver wells.ns.cloudflare.com is published for finceptor.app in the registration record from https://pubapi.registry.google/rdap/domain/finceptor.app.
DNS
finceptor.app has 4 address records, 5 mail exchangers and 2 nameservers, measured at 1.1.1.1:53.
| A | 188.114.96.3, 188.114.97.3 |
|---|---|
| AAAA | 2a06:98c1:3120::3, 2a06:98c1:3121::3 |
| NS | bristol.ns.cloudflare.com, wells.ns.cloudflare.com |
| MX | aspmx.l.google.com (1) Google, alt1.aspmx.l.google.com (5) Google, alt2.aspmx.l.google.com (5) Google, alt3.aspmx.l.google.com (10) Google, alt4.aspmx.l.google.com (10) Google |
| SPF | present |
| DMARC | absent |
| CAA | — |
| Wildcard | off |
| DNSSEC | not signed |
| Resolver | 1.1.1.1:53 |
The SPF text record at finceptor.app is "v=spf1 include:_spf.google.com include:sendersrv.com-all".
IPv4 address 188.114.96.3 answers for finceptor.app at resolver 1.1.1.1:53.
IPv4 address 188.114.97.3 answers for finceptor.app at resolver 1.1.1.1:53.
IPv6 address 2a06:98c1:3120::3 answers for finceptor.app at resolver 1.1.1.1:53.
IPv6 address 2a06:98c1:3121::3 answers for finceptor.app at resolver 1.1.1.1:53.
Mail exchanger aspmx.l.google.com has preference 1. The host is recognised as Google.
Mail exchanger alt1.aspmx.l.google.com has preference 5. The host is recognised as Google.
Mail exchanger alt2.aspmx.l.google.com has preference 5. The host is recognised as Google.
Mail exchanger alt3.aspmx.l.google.com has preference 10. The host is recognised as Google.
Mail exchanger alt4.aspmx.l.google.com has preference 10. The host is recognised as Google.
Hosting and geo
finceptor.app is placed in Toronto, Canada by the local geolocation database (db-ip).
| Address | 188.114.96.3 |
|---|---|
| Country | Canada |
| City | Toronto |
| Source | db-ip |
SSL/TLS
The certificate for finceptor.app is valid, with 40 days left and 2 subject alternative names. Source: tls:443.
| Issuer | WE1 |
|---|---|
| Subject | finceptor.app |
| Valid from | 11 September 2026 |
| Valid until | 10 December 2026 |
| Days left | 40 |
| SAN count | 2 |
| Protocol | TLS 1.3 |
| Source | tls:443 |
Subject alternative names: *.finceptor.app, finceptor.app.
Tech stack
Tech detection checked the fetched homepage and named 4 products. Source: wappalyzergo.
- Cloudflare · CDN
- HSTS · Security
- HTTP/3 · Miscellaneous
- Vercel · PaaS
Cloudflare is filed under CDN.
HSTS is filed under Security.
HTTP/3 is filed under Miscellaneous.
Vercel is filed under PaaS.
On-page checks
The homepage returned HTTP 200 in 190 ms. The target title is 61 characters and the page has 1 H1 heading.
| Status | 200 |
|---|---|
| TTFB | 190 ms |
| Title length | 61 no |
| Quoted title | "Finceptor: Invest in Tomorrow's Emerging Web3 Unicorns, Today" |
| Meta description | "Become an early investor of Web3's top projects with over 250,000 other backers." yes |
| H1 count | 1 |
| HSTS | yes yes |
| CSP | no |
| X-Frame-Options | DENY |
| Robots meta | — |
| Canonical | — |
| Language | en |
| Links | 59 |
| Images | 28 |
| 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 finceptor.app 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 | yes |
| 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 10 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
First checked on 30 October 2026; changes will appear here.
Questions
Is finceptor.app 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 finceptor.app?
finceptor.app is placed in Toronto, Canada.
When does finceptor.app expire?
finceptor.app expires on 27 April 2028 according to https://pubapi.registry.google/rdap/domain/finceptor.app.
Who owns finceptor.app?
The registry did not return a person or a company for finceptor.app. RDAP often redacts the registrant. The registrar on file is GoDaddy.com, LLC.
Sources
- RDAP source https://pubapi.registry.google/rdap/domain/finceptor.app at 2026-10-30T13:31:30Z
- DNS source 1.1.1.1:53 at 2026-10-30T13:31:30Z
- TLS source tls:443 at 2026-10-30T13:31:30Z
- HTTP source https://finceptor.app/ at 2026-10-30T13:31:30Z
- Tech source wappalyzergo at 2026-10-30T13:31:30Z
- Geo source db-ip at 2026-10-30T13:31:30Z
- Safety source family DNS and local lists at 2026-10-30T13:31:30Z
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.