hornyfanz.com
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
Online · 200Family DNS blockedSSL: 78 days left5 years old
50
hornyfanz.com was registered on 27 Dec 2020 via PDR Ltd. d/b/a PublicDomainRegistry.com and the registry expiry is 27 Dec 2026. WHOIS data came from RDAP at https://rdap.verisign.com/com/v1/domain/hornyfanz.com.
hornyfanz.com publishes 2 nameservers. DNSSEC is not signed.
hornyfanz.com has 2 IPv4 addresses (104.21.85.143, 172.67.206.168) and 2 IPv6 addresses (2606:4700:3030::6815:558f, 2606:4700:3033::ac43:cea8). The geolocation database places 104.21.85.143 in Toronto, Canada.
The TLS certificate from WE1 is valid and has 78 days left (TLS 1.3). The homepage answered HTTP 200.
Tech detection named Cloudflare, ContentViews, Elementor, Google Analytics, HTTP/3, MySQL, Nginx, PHP, Site Kit, Swiper, W3 Total Cache, WordPress, Yoast SEO, jQuery and jQuery Migrate. The fingerprints ran on the homepage that was already downloaded.
Domain · RDAP/WHOIS
hornyfanz.com was registered on 27 Dec 2020 via PDR Ltd. d/b/a PublicDomainRegistry.com. The registry returned 1 status value and 2 nameservers from https://rdap.verisign.com/com/v1/domain/hornyfanz.com.
| Registered | since 27 Dec 2020 |
|---|---|
| Created | 27 December 2020 |
| Updated | 18 December 2025 |
| Expires | 27 December 2026 |
| Registrar | PDR Ltd. d/b/a PublicDomainRegistry.com |
| Status | client transfer prohibited |
| Nameservers | lucy.ns.cloudflare.com, matteo.ns.cloudflare.com |
| DNSSEC | no |
| Source | https://rdap.verisign.com/com/v1/domain/hornyfanz.com |
hornyfanz.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 lucy.ns.cloudflare.com is published for hornyfanz.com in the registration record from https://rdap.verisign.com/com/v1/domain/hornyfanz.com.
Nameserver matteo.ns.cloudflare.com is published for hornyfanz.com in the registration record from https://rdap.verisign.com/com/v1/domain/hornyfanz.com.
DNS
hornyfanz.com has 4 address records, 1 mail exchanger and 2 nameservers, measured at 1.1.1.1:53.
| A | 104.21.85.143, 172.67.206.168 |
|---|---|
| AAAA | 2606:4700:3030::6815:558f, 2606:4700:3033::ac43:cea8 |
| NS | lucy.ns.cloudflare.com, matteo.ns.cloudflare.com |
| MX | _dc-mx.d6e8432f10a4.hornyfanz.com (10) |
| SPF | absent |
| DMARC | absent |
| CAA | — |
| Wildcard | off |
| DNSSEC | not signed |
| Resolver | 1.1.1.1:53 |
IPv4 address 104.21.85.143 answers for hornyfanz.com at resolver 1.1.1.1:53.
IPv4 address 172.67.206.168 answers for hornyfanz.com at resolver 1.1.1.1:53.
IPv6 address 2606:4700:3030::6815:558f answers for hornyfanz.com at resolver 1.1.1.1:53.
IPv6 address 2606:4700:3033::ac43:cea8 answers for hornyfanz.com at resolver 1.1.1.1:53.
Mail exchanger _dc-mx.d6e8432f10a4.hornyfanz.com has preference 10.
Hosting and geo
hornyfanz.com is placed in Toronto, Canada by the local geolocation database (db-ip).
| Address | 104.21.85.143 |
|---|---|
| Country | Canada |
| City | Toronto |
| Source | db-ip |
SSL/TLS
The certificate for hornyfanz.com is valid, with 78 days left and 2 subject alternative names. Source: tls:443.
| Issuer | WE1 |
|---|---|
| Subject | hornyfanz.com |
| Valid from | 19 October 2026 |
| Valid until | 17 January 2027 |
| Days left | 78 |
| SAN count | 2 |
| Protocol | TLS 1.3 |
| Source | tls:443 |
Subject alternative names: *.hornyfanz.com, hornyfanz.com.
Tech stack
Tech detection checked the fetched homepage and named 15 products. Source: wappalyzergo.
- Cloudflare · CDN
- ContentViews · Widgets, WordPress plugins
- Elementor · Page builders, WordPress plugins
- Google Analytics · Analytics
- HTTP/3 · Miscellaneous
- MySQL · Databases
- Nginx · Web servers, Reverse proxies
- PHP · Programming languages
- Site Kit · Analytics, WordPress plugins
- Swiper · JavaScript libraries
- W3 Total Cache · Caching, WordPress plugins
- WordPress · CMS, Blogs
- Yoast SEO · SEO, WordPress plugins
- jQuery · JavaScript libraries
- jQuery Migrate · JavaScript libraries
Cloudflare is filed under CDN.
ContentViews is filed under Widgets, WordPress plugins.
Elementor is filed under Page builders, WordPress plugins.
Google Analytics is filed under Analytics.
HTTP/3 is filed under Miscellaneous.
MySQL is filed under Databases.
Nginx is filed under Web servers, Reverse proxies.
PHP is filed under Programming languages.
Site Kit is filed under Analytics, WordPress plugins.
Swiper is filed under JavaScript libraries.
W3 Total Cache is filed under Caching, WordPress plugins.
WordPress is filed under CMS, Blogs.
Yoast SEO is filed under SEO, WordPress plugins.
jQuery is filed under JavaScript libraries.
jQuery Migrate is filed under JavaScript libraries.
On-page checks
The homepage returned HTTP 200 in 32 ms. The target title is 48 characters and the page has 1 H1 heading.
| Status | 200 |
|---|---|
| TTFB | 32 ms |
| Title length | 48 yes |
| Quoted title | "HornySimp – Free 1080p Porn & Top OnlyFans Stars" |
| Meta description | "Watch daily 1080p full-length porn, premium studio scenes, and trending OnlyFans stars—free, fast, and made for adult fans in the US, UK, CA & AU." yes |
| H1 count | 1 |
| HSTS | no no |
| CSP | no |
| X-Frame-Options | — |
| Robots meta | index, follow, max-image-preview:large, max-snippet:-1, max-video-preview:-1 |
| Canonical | https://hornysimp.com/ |
| Language | en-US |
| Links | 135 |
| Images | 62 |
| 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 hornyfanz.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 hornyfanz.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 hornyfanz.com safe?
Cloudflare family DNS returned a block for hornyfanz.com. That resolver covers adult and malware names.
Who hosts hornyfanz.com?
hornyfanz.com is placed in Toronto, Canada.
When does hornyfanz.com expire?
hornyfanz.com expires on 27 December 2026 according to https://rdap.verisign.com/com/v1/domain/hornyfanz.com.
Who owns hornyfanz.com?
The registry did not return a person or a company for hornyfanz.com. RDAP often redacts the registrant. The registrar on file is PDR Ltd. d/b/a PublicDomainRegistry.com.
Sources
- RDAP source https://rdap.verisign.com/com/v1/domain/hornyfanz.com at 2026-10-30T13:57:57Z
- DNS source 1.1.1.1:53 at 2026-10-30T13:57:57Z
- TLS source tls:443 at 2026-10-30T13:57:57Z
- HTTP source https://hornyfanz.com/ at 2026-10-30T13:57:57Z
- Tech source wappalyzergo at 2026-10-30T13:57:57Z
- Geo source db-ip at 2026-10-30T13:57:57Z
- Safety source family DNS and local lists at 2026-10-30T13:57:57Z
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.