shavepage.com
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
Online · 200SafeSSL: 79 days left10 years old
80
shavepage.com was registered on 22 Sep 2016 via Cloudflare, Inc. and the registry expiry is 22 Sep 2027. WHOIS data came from RDAP at https://rdap.verisign.com/com/v1/domain/shavepage.com.
shavepage.com publishes 2 nameservers. DNSSEC is signed.
shavepage.com has 2 IPv4 addresses (104.21.23.186, 172.67.212.190) and 2 IPv6 addresses (2606:4700:3031::ac43:d4be, 2606:4700:3034::6815:17ba). The geolocation database places 104.21.23.186 in Toronto, Canada.
The TLS certificate from WE1 is valid and has 79 days left (TLS 1.3). The homepage answered HTTP 200.
Tech detection named Cloudflare, Google Analytics, HTTP/3, MySQL, PHP, Packery, ShareThis, Slider Revolution, WordPress, Yoast SEO, jQuery and jQuery Migrate. The fingerprints ran on the homepage that was already downloaded.
No safety warning was recorded for shavepage.com in the checks that ran.
Domain · RDAP/WHOIS
shavepage.com was registered on 22 Sep 2016 via Cloudflare, Inc.. The registry returned 1 status value and 2 nameservers from https://rdap.verisign.com/com/v1/domain/shavepage.com.
| Registered | since 22 Sep 2016 |
|---|---|
| Created | 22 September 2016 |
| Updated | 23 August 2026 |
| Expires | 22 September 2027 |
| Registrar | Cloudflare, Inc. |
| Status | client transfer prohibited |
| Nameservers | joyce.ns.cloudflare.com, merlin.ns.cloudflare.com |
| DNSSEC | yes |
| Source | https://rdap.verisign.com/com/v1/domain/shavepage.com |
shavepage.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 joyce.ns.cloudflare.com is published for shavepage.com in the registration record from https://rdap.verisign.com/com/v1/domain/shavepage.com.
Nameserver merlin.ns.cloudflare.com is published for shavepage.com in the registration record from https://rdap.verisign.com/com/v1/domain/shavepage.com.
DNS
shavepage.com has 4 address records, 1 mail exchanger and 2 nameservers, measured at 1.1.1.1:53.
| A | 104.21.23.186, 172.67.212.190 |
|---|---|
| AAAA | 2606:4700:3031::ac43:d4be, 2606:4700:3034::6815:17ba |
| NS | joyce.ns.cloudflare.com, merlin.ns.cloudflare.com |
| MX | mail.shavepage.com (10) |
| SPF | present |
| DMARC | present |
| CAA | — |
| Wildcard | on |
| DNSSEC | signed |
| Resolver | 1.1.1.1:53 |
The SPF text record at shavepage.com is "v=spf1 ip4:72.167.35.145 include:secureserver.net ~all".
The DMARC text record at _dmarc.shavepage.com is "v=DMARC1; p=none; rua=mailto:[email protected]".
IPv4 address 104.21.23.186 answers for shavepage.com at resolver 1.1.1.1:53.
IPv4 address 172.67.212.190 answers for shavepage.com at resolver 1.1.1.1:53.
IPv6 address 2606:4700:3031::ac43:d4be answers for shavepage.com at resolver 1.1.1.1:53.
IPv6 address 2606:4700:3034::6815:17ba answers for shavepage.com at resolver 1.1.1.1:53.
Mail exchanger mail.shavepage.com has preference 10.
A random label under shavepage.com also resolved, which means wildcard DNS is on.
Hosting and geo
shavepage.com is placed in Toronto, Canada by the local geolocation database (db-ip).
| Address | 104.21.23.186 |
|---|---|
| Country | Canada |
| City | Toronto |
| Source | db-ip |
SSL/TLS
The certificate for shavepage.com is valid, with 79 days left and 2 subject alternative names. Source: tls:443.
| Issuer | WE1 |
|---|---|
| Subject | shavepage.com |
| Valid from | 20 October 2026 |
| Valid until | 18 January 2027 |
| Days left | 79 |
| SAN count | 2 |
| Protocol | TLS 1.3 |
| Source | tls:443 |
Subject alternative names: *.shavepage.com, shavepage.com.
Tech stack
Tech detection checked the fetched homepage and named 12 products. Source: wappalyzergo.
- Cloudflare · CDN
- Google Analytics · Analytics
- HTTP/3 · Miscellaneous
- MySQL · Databases
- PHP · Programming languages
- Packery · JavaScript libraries
- ShareThis · Widgets
- Slider Revolution · Widgets, Photo galleries
- WordPress · CMS, Blogs
- Yoast SEO · SEO, WordPress plugins
- jQuery · JavaScript libraries
- jQuery Migrate · JavaScript libraries
Cloudflare is filed under CDN.
Google Analytics is filed under Analytics.
HTTP/3 is filed under Miscellaneous.
MySQL is filed under Databases.
PHP is filed under Programming languages.
Packery is filed under JavaScript libraries.
ShareThis is filed under Widgets.
Slider Revolution is filed under Widgets, Photo galleries.
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 3397 ms. The target title is 45 characters and the page has 4 H1 headings.
| Status | 200 |
|---|---|
| TTFB | 3397 ms |
| Title length | 45 yes |
| Quoted title | "Fetish Haircut & Headshave Videos - Shavepage" |
| Meta description | "Haircut, headshave and bald fetish videos for people who are looking for bald fetish or haircut fetish photos, stories and videos." yes |
| H1 count | 4 |
| 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://shavepage.com/ |
| Language | en-US |
| Links | 131 |
| Images | 284 |
| 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 shavepage.com 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 | no |
| 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 15 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 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 shavepage.com 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 shavepage.com?
shavepage.com is placed in Toronto, Canada.
When does shavepage.com expire?
shavepage.com expires on 22 September 2027 according to https://rdap.verisign.com/com/v1/domain/shavepage.com.
Who owns shavepage.com?
The registry did not return a person or a company for shavepage.com. RDAP often redacts the registrant. The registrar on file is Cloudflare, Inc..
Sources
- RDAP source https://rdap.verisign.com/com/v1/domain/shavepage.com at 2026-10-30T14:13:51Z
- DNS source 1.1.1.1:53 at 2026-10-30T14:13:51Z
- TLS source tls:443 at 2026-10-30T14:13:51Z
- HTTP source https://shavepage.com/ at 2026-10-30T14:13:51Z
- Tech source wappalyzergo at 2026-10-30T14:13:51Z
- Geo source db-ip at 2026-10-30T14:13:51Z
- Safety source family DNS and local lists at 2026-10-30T14:13:51Z
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.