hornyfans.com
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
Online · 200Family DNS blockedSSL: 30 days left8 years old
60
hornyfans.com was registered on 20 Jun 2018 via Porkbun LLC and the registry expiry is 20 Jun 2028. WHOIS data came from RDAP at https://rdap.verisign.com/com/v1/domain/hornyfans.com.
hornyfans.com publishes 2 nameservers. DNSSEC is not signed.
hornyfans.com 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 30 days left (TLS 1.3). The homepage answered HTTP 200.
Tech detection named Bootstrap, Cloudflare, HTTP/3, Moment.js, Popper, Statically, SweetAlert2, ZURB Foundation, cdnjs, jQuery and jsDelivr. The fingerprints ran on the homepage that was already downloaded.
Domain · RDAP/WHOIS
hornyfans.com was registered on 20 Jun 2018 via Porkbun LLC. The registry returned 2 status values and 2 nameservers from https://rdap.verisign.com/com/v1/domain/hornyfans.com.
| Registered | since 20 Jun 2018 |
|---|---|
| Created | 20 June 2018 |
| Updated | 28 October 2026 |
| Expires | 20 June 2028 |
| Registrar | Porkbun LLC |
| Status | client delete prohibited, client transfer prohibited |
| Nameservers | amy.ns.cloudflare.com, kirk.ns.cloudflare.com |
| DNSSEC | no |
| Source | https://rdap.verisign.com/com/v1/domain/hornyfans.com |
hornyfans.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.
hornyfans.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 amy.ns.cloudflare.com is published for hornyfans.com in the registration record from https://rdap.verisign.com/com/v1/domain/hornyfans.com.
Nameserver kirk.ns.cloudflare.com is published for hornyfans.com in the registration record from https://rdap.verisign.com/com/v1/domain/hornyfans.com.
DNS
hornyfans.com has 4 address records, 3 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 | amy.ns.cloudflare.com, kirk.ns.cloudflare.com |
| MX | route3.mx.cloudflare.net (24), route1.mx.cloudflare.net (38), route2.mx.cloudflare.net (47) |
| SPF | present |
| DMARC | present |
| CAA | — |
| Wildcard | off |
| DNSSEC | not signed |
| Resolver | 1.1.1.1:53 |
The SPF text record at hornyfans.com is "v=spf1 include:_spf.mx.cloudflare.net ~all".
The DMARC text record at _dmarc.hornyfans.com is "v=DMARC1; p=none; pct=100".
IPv4 address 188.114.96.3 answers for hornyfans.com at resolver 1.1.1.1:53.
IPv4 address 188.114.97.3 answers for hornyfans.com at resolver 1.1.1.1:53.
IPv6 address 2a06:98c1:3120::3 answers for hornyfans.com at resolver 1.1.1.1:53.
IPv6 address 2a06:98c1:3121::3 answers for hornyfans.com at resolver 1.1.1.1:53.
Mail exchanger route3.mx.cloudflare.net has preference 24.
Mail exchanger route1.mx.cloudflare.net has preference 38.
Mail exchanger route2.mx.cloudflare.net has preference 47.
Hosting and geo
hornyfans.com 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 hornyfans.com is valid, with 30 days left and 2 subject alternative names. Source: tls:443.
| Issuer | WE1 |
|---|---|
| Subject | hornyfans.com |
| Valid from | 1 September 2026 |
| Valid until | 30 November 2026 |
| Days left | 30 |
| SAN count | 2 |
| Protocol | TLS 1.3 |
| Source | tls:443 |
Subject alternative names: *.hornyfans.com, hornyfans.com.
Tech stack
Tech detection checked the fetched homepage and named 11 products. Source: wappalyzergo.
- Bootstrap · UI frameworks
- Cloudflare · CDN
- HTTP/3 · Miscellaneous
- Moment.js · JavaScript libraries
- Popper · Miscellaneous
- Statically · CDN
- SweetAlert2 · JavaScript libraries
- ZURB Foundation · UI frameworks
- cdnjs · CDN
- jQuery · JavaScript libraries
- jsDelivr · CDN
Bootstrap is filed under UI frameworks.
Cloudflare is filed under CDN.
HTTP/3 is filed under Miscellaneous.
Moment.js is filed under JavaScript libraries.
Popper is filed under Miscellaneous.
Statically is filed under CDN.
SweetAlert2 is filed under JavaScript libraries.
ZURB Foundation is filed under UI frameworks.
cdnjs is filed under CDN.
jQuery is filed under JavaScript libraries.
jsDelivr is filed under CDN.
On-page checks
The homepage returned HTTP 200 in 44 ms. The target title is 45 characters and the page has 4 H1 headings.
| Status | 200 |
|---|---|
| TTFB | 44 ms |
| Title length | 45 yes |
| Quoted title | "Hornyfans - Adult content creators on MachoBB" |
| Meta description | "HornyFans: link tree for gay adult content creators on MachoBB. Centralize OnlyFans, socials and contact on one page, uncensored." yes |
| H1 count | 4 |
| HSTS | no no |
| CSP | no |
| X-Frame-Options | — |
| Robots meta | index, follow |
| Canonical | https://www.hornyfans.com/en |
| Language | — |
| Links | 16 |
| Images | 18 |
| 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 hornyfans.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 hornyfans.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 10 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 hornyfans.com safe?
Cloudflare family DNS returned a block for hornyfans.com. That resolver covers adult and malware names.
Who hosts hornyfans.com?
hornyfans.com is placed in Toronto, Canada.
When does hornyfans.com expire?
hornyfans.com expires on 20 June 2028 according to https://rdap.verisign.com/com/v1/domain/hornyfans.com.
Who owns hornyfans.com?
The registry did not return a person or a company for hornyfans.com. RDAP often redacts the registrant. The registrar on file is Porkbun LLC.
Sources
- RDAP source https://rdap.verisign.com/com/v1/domain/hornyfans.com at 2026-10-30T13:57:56Z
- DNS source 1.1.1.1:53 at 2026-10-30T13:57:56Z
- TLS source tls:443 at 2026-10-30T13:57:56Z
- HTTP source https://hornyfans.com/ at 2026-10-30T13:57:56Z
- Tech source wappalyzergo at 2026-10-30T13:57:56Z
- Geo source db-ip at 2026-10-30T13:57:56Z
- Safety source family DNS and local lists at 2026-10-30T13:57:56Z
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.