hotmenuniverse.com
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
Online · 200Family DNS blockedSSL: 31 days left6 years oldTranco #852451
60
hotmenuniverse.com was registered on 4 Apr 2020 via NameSilo, LLC and the registry expiry is 4 Apr 2029. WHOIS data came from RDAP at https://rdap.verisign.com/com/v1/domain/hotmenuniverse.com.
hotmenuniverse.com publishes 2 nameservers. DNSSEC is not signed.
hotmenuniverse.com has 3 IPv4 addresses (104.26.6.84, 104.26.7.84, 172.67.70.227) and 3 IPv6 addresses (2606:4700:20::681a:654, 2606:4700:20::681a:754, 2606:4700:20::ac43:46e3). The geolocation database places 104.26.6.84 in Toronto, Canada.
The TLS certificate from WE1 is valid and has 31 days left (TLS 1.3). The homepage answered HTTP 200.
Tech detection named Cloudflare, HTTP/3, MySQL, PHP, WP-Optimize, WordPress, WordPress Block Editor, jQuery and jQuery Migrate. The fingerprints ran on the homepage that was already downloaded.
Domain · RDAP/WHOIS
hotmenuniverse.com was registered on 4 Apr 2020 via NameSilo, LLC. The registry returned 1 status value and 2 nameservers from https://rdap.verisign.com/com/v1/domain/hotmenuniverse.com.
| Registered | since 4 Apr 2020 |
|---|---|
| Created | 4 April 2020 |
| Updated | 19 March 2025 |
| Expires | 4 April 2029 |
| Registrar | NameSilo, LLC |
| Status | client transfer prohibited |
| Nameservers | hera.ns.cloudflare.com, memphis.ns.cloudflare.com |
| DNSSEC | no |
| Source | https://rdap.verisign.com/com/v1/domain/hotmenuniverse.com |
hotmenuniverse.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 hera.ns.cloudflare.com is published for hotmenuniverse.com in the registration record from https://rdap.verisign.com/com/v1/domain/hotmenuniverse.com.
Nameserver memphis.ns.cloudflare.com is published for hotmenuniverse.com in the registration record from https://rdap.verisign.com/com/v1/domain/hotmenuniverse.com.
DNS
hotmenuniverse.com has 6 address records, 2 mail exchangers and 2 nameservers, measured at 1.1.1.1:53.
| A | 104.26.6.84, 104.26.7.84, 172.67.70.227 |
|---|---|
| AAAA | 2606:4700:20::681a:654, 2606:4700:20::681a:754, 2606:4700:20::ac43:46e3 |
| NS | hera.ns.cloudflare.com, memphis.ns.cloudflare.com |
| MX | mx1.privateemail.com (10), mx2.privateemail.com (10) |
| SPF | present |
| DMARC | present |
| CAA | — |
| Wildcard | off |
| DNSSEC | not signed |
| Resolver | 1.1.1.1:53 |
The SPF text record at hotmenuniverse.com is "v=spf1 include:spf.privateemail.com ~all".
The DMARC text record at _dmarc.hotmenuniverse.com is "v=DMARC1; p=none; rua=mailto:[email protected]".
IPv4 address 104.26.6.84 answers for hotmenuniverse.com at resolver 1.1.1.1:53.
IPv4 address 104.26.7.84 answers for hotmenuniverse.com at resolver 1.1.1.1:53.
IPv4 address 172.67.70.227 answers for hotmenuniverse.com at resolver 1.1.1.1:53.
IPv6 address 2606:4700:20::681a:654 answers for hotmenuniverse.com at resolver 1.1.1.1:53.
IPv6 address 2606:4700:20::681a:754 answers for hotmenuniverse.com at resolver 1.1.1.1:53.
IPv6 address 2606:4700:20::ac43:46e3 answers for hotmenuniverse.com at resolver 1.1.1.1:53.
Mail exchanger mx1.privateemail.com has preference 10.
Mail exchanger mx2.privateemail.com has preference 10.
Hosting and geo
hotmenuniverse.com is placed in Toronto, Canada by the local geolocation database (db-ip).
| Address | 104.26.6.84 |
|---|---|
| Country | Canada |
| City | Toronto |
| Source | db-ip |
SSL/TLS
The certificate for hotmenuniverse.com is valid, with 31 days left and 2 subject alternative names. Source: tls:443.
| Issuer | WE1 |
|---|---|
| Subject | hotmenuniverse.com |
| Valid from | 2 September 2026 |
| Valid until | 1 December 2026 |
| Days left | 31 |
| SAN count | 2 |
| Protocol | TLS 1.3 |
| Source | tls:443 |
Subject alternative names: *.hotmenuniverse.com, hotmenuniverse.com.
Tech stack
Tech detection checked the fetched homepage and named 9 products. Source: wappalyzergo.
- Cloudflare · CDN
- HTTP/3 · Miscellaneous
- MySQL · Databases
- PHP · Programming languages
- WP-Optimize · WordPress plugins, Performance
- WordPress · CMS, Blogs
- WordPress Block Editor · Page builders
- jQuery · JavaScript libraries
- jQuery Migrate · JavaScript libraries
Cloudflare is filed under CDN.
HTTP/3 is filed under Miscellaneous.
MySQL is filed under Databases.
PHP is filed under Programming languages.
WP-Optimize is filed under WordPress plugins, Performance.
WordPress is filed under CMS, Blogs.
WordPress Block Editor is filed under Page builders.
jQuery is filed under JavaScript libraries.
jQuery Migrate is filed under JavaScript libraries.
On-page checks
The homepage returned HTTP 200 in 167 ms. The target title is 76 characters and the page has 0 H1 headings.
| Status | 200 |
|---|---|
| TTFB | 167 ms |
| Title length | 76 no |
| Quoted title | "Hot Men Universe – The Hottest Men and the Hottest Gay Porn in the Universe!" |
| Meta description | none no |
| H1 count | 0 |
| HSTS | no no |
| CSP | no |
| X-Frame-Options | — |
| Robots meta | max-image-preview:large |
| Canonical | — |
| Language | en-US |
| Links | 102 |
| Images | 16 |
| 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 hotmenuniverse.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 hotmenuniverse.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 hotmenuniverse.com safe?
Cloudflare family DNS returned a block for hotmenuniverse.com. That resolver covers adult and malware names.
Who hosts hotmenuniverse.com?
hotmenuniverse.com is placed in Toronto, Canada.
When does hotmenuniverse.com expire?
hotmenuniverse.com expires on 4 April 2029 according to https://rdap.verisign.com/com/v1/domain/hotmenuniverse.com.
Who owns hotmenuniverse.com?
The registry did not return a person or a company for hotmenuniverse.com. RDAP often redacts the registrant. The registrar on file is NameSilo, LLC.
Sources
- RDAP source https://rdap.verisign.com/com/v1/domain/hotmenuniverse.com at 2026-10-30T13:58:01Z
- DNS source 1.1.1.1:53 at 2026-10-30T13:58:01Z
- TLS source tls:443 at 2026-10-30T13:58:01Z
- HTTP source https://hotmenuniverse.com/ at 2026-10-30T13:58:01Z
- Tech source wappalyzergo at 2026-10-30T13:58:01Z
- Geo source db-ip at 2026-10-30T13:58:01Z
- Safety source family DNS and local lists at 2026-10-30T13:58:01Z
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.