fapeza.com
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
Online · 200Family DNS blockedSSL: 59 days left4 years oldTranco #39549
50
fapeza.com was registered on 16 May 2022 via NameSilo, LLC and the registry expiry is 16 May 2027. WHOIS data came from RDAP at https://rdap.verisign.com/com/v1/domain/fapeza.com.
fapeza.com publishes 2 nameservers. DNSSEC is not signed.
fapeza.com has 3 IPv4 addresses (104.26.2.104, 104.26.3.104, 172.67.68.198) and 3 IPv6 addresses (2606:4700:20::681a:268, 2606:4700:20::681a:368, 2606:4700:20::ac43:44c6). The geolocation database places 104.26.2.104 in Toronto, Canada.
The TLS certificate from WE1 is valid and has 59 days left (TLS 1.3). The homepage answered HTTP 200.
Tech detection named Cloudflare and Google Analytics. The fingerprints ran on the homepage that was already downloaded.
Domain · RDAP/WHOIS
fapeza.com was registered on 16 May 2022 via NameSilo, LLC. The registry returned 1 status value and 2 nameservers from https://rdap.verisign.com/com/v1/domain/fapeza.com.
| Registered | since 16 May 2022 |
|---|---|
| Created | 16 May 2022 |
| Updated | 16 April 2026 |
| Expires | 16 May 2027 |
| Registrar | NameSilo, LLC |
| Status | client transfer prohibited |
| Nameservers | giancarlo.ns.cloudflare.com, kim.ns.cloudflare.com |
| DNSSEC | no |
| Source | https://rdap.verisign.com/com/v1/domain/fapeza.com |
fapeza.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.
Nameserver giancarlo.ns.cloudflare.com is published for fapeza.com in the registration record from https://rdap.verisign.com/com/v1/domain/fapeza.com.
Nameserver kim.ns.cloudflare.com is published for fapeza.com in the registration record from https://rdap.verisign.com/com/v1/domain/fapeza.com.
DNS
fapeza.com has 6 address records, 0 mail exchangers and 2 nameservers, measured at 1.1.1.1:53.
| A | 104.26.2.104, 104.26.3.104, 172.67.68.198 |
|---|---|
| AAAA | 2606:4700:20::681a:268, 2606:4700:20::681a:368, 2606:4700:20::ac43:44c6 |
| NS | giancarlo.ns.cloudflare.com, kim.ns.cloudflare.com |
| MX | — |
| SPF | absent |
| DMARC | absent |
| CAA | — |
| Wildcard | off |
| DNSSEC | not signed |
| Resolver | 1.1.1.1:53 |
IPv4 address 104.26.2.104 answers for fapeza.com at resolver 1.1.1.1:53.
IPv4 address 104.26.3.104 answers for fapeza.com at resolver 1.1.1.1:53.
IPv4 address 172.67.68.198 answers for fapeza.com at resolver 1.1.1.1:53.
IPv6 address 2606:4700:20::681a:268 answers for fapeza.com at resolver 1.1.1.1:53.
IPv6 address 2606:4700:20::681a:368 answers for fapeza.com at resolver 1.1.1.1:53.
IPv6 address 2606:4700:20::ac43:44c6 answers for fapeza.com at resolver 1.1.1.1:53.
Hosting and geo
fapeza.com is placed in Toronto, Canada by the local geolocation database (db-ip).
| Address | 104.26.2.104 |
|---|---|
| Country | Canada |
| City | Toronto |
| Source | db-ip |
SSL/TLS
The certificate for fapeza.com is valid, with 59 days left and 2 subject alternative names. Source: tls:443.
| Issuer | WE1 |
|---|---|
| Subject | fapeza.com |
| Valid from | 30 September 2026 |
| Valid until | 29 December 2026 |
| Days left | 59 |
| SAN count | 2 |
| Protocol | TLS 1.3 |
| Source | tls:443 |
Subject alternative names: *.fapeza.com, fapeza.com.
Tech stack
Tech detection checked the fetched homepage and named 2 products. Source: wappalyzergo.
- Cloudflare · CDN
- Google Analytics · Analytics
Cloudflare is filed under CDN.
Google Analytics is filed under Analytics.
On-page checks
The homepage returned HTTP 200 in 75 ms. The target title is 6 characters and the page has 0 H1 headings.
| Status | 200 |
|---|---|
| TTFB | 75 ms |
| Title length | 6 yes |
| Quoted title | "Fapeza" |
| Meta description | none no |
| H1 count | 0 |
| HSTS | no no |
| CSP | no |
| X-Frame-Options | — |
| Robots meta | — |
| Canonical | https://fapeza.com/ |
| Language | en |
| Links | 120 |
| Images | 44 |
| 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 fapeza.com is blocked, and URLhaus is clear. Source: family DNS and local lists.
| Family DNS | blocked |
|---|---|
| URLhaus | clear |
| UT1 | — |
| Web Risk | not run |
| Source | family DNS and local lists |
| HSTS | no |
| CSP | no |
Cloudflare family DNS returned a block for fapeza.com. That resolver covers adult and malware names.
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 0 of 20. SPF, DMARC, CAA, and DNSSEC are five points each.
Security headers 0 of 15. HSTS, CSP, and X-Frame-Options or CSP frame-ancestors.
Safety lists 0 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 fapeza.com safe?
Cloudflare family DNS returned a block for fapeza.com. That resolver covers adult and malware names.
Who hosts fapeza.com?
fapeza.com is placed in Toronto, Canada.
When does fapeza.com expire?
fapeza.com expires on 16 May 2027 according to https://rdap.verisign.com/com/v1/domain/fapeza.com.
Who owns fapeza.com?
The registry did not return a person or a company for fapeza.com. RDAP often redacts the registrant. The registrar on file is NameSilo, LLC.
Sources
- RDAP source https://rdap.verisign.com/com/v1/domain/fapeza.com at 2026-10-30T13:54:06Z
- DNS source 1.1.1.1:53 at 2026-10-30T13:54:06Z
- TLS source tls:443 at 2026-10-30T13:54:06Z
- HTTP source https://fapeza.com/ at 2026-10-30T13:54:06Z
- Tech source wappalyzergo at 2026-10-30T13:54:06Z
- Geo source db-ip at 2026-10-30T13:54:06Z
- Safety source family DNS and local lists at 2026-10-30T13:54:06Z
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.