pornsheriff.com
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
Online · 200Family DNS blockedSSL: 73 days left6 years old
50
pornsheriff.com was registered on 8 Oct 2020 via 123-Reg Limited and the registry expiry is 8 Oct 2029. WHOIS data came from RDAP at https://rdap.verisign.com/com/v1/domain/pornsheriff.com.
pornsheriff.com publishes 2 nameservers. DNSSEC is not signed.
pornsheriff.com has 2 IPv4 addresses (188.114.96.3, 188.114.97.3) and 2 IPv6 addresses (2a06:98c1:3120::4, 2a06:98c1:3121::4). The geolocation database places 188.114.96.3 in Toronto, Canada.
The TLS certificate from WE1 is valid and has 73 days left (TLS 1.3). The homepage answered HTTP 200.
Tech detection named Age Gate, Cloudflare, HTTP/3, Modern Image Formats, MySQL, PHP, Speculative Loading, W3 Total Cache, WPMU DEV Smush, WordPress and Yoast SEO. The fingerprints ran on the homepage that was already downloaded.
Domain · RDAP/WHOIS
pornsheriff.com was registered on 8 Oct 2020 via 123-Reg Limited. The registry returned 1 status value and 2 nameservers from https://rdap.verisign.com/com/v1/domain/pornsheriff.com.
| Registered | since 8 Oct 2020 |
|---|---|
| Created | 8 October 2020 |
| Updated | 9 October 2026 |
| Expires | 8 October 2029 |
| Registrar | 123-Reg Limited |
| Status | active |
| Nameservers | margaret.ns.cloudflare.com, terry.ns.cloudflare.com |
| DNSSEC | no |
| Source | https://rdap.verisign.com/com/v1/domain/pornsheriff.com |
Nameserver margaret.ns.cloudflare.com is published for pornsheriff.com in the registration record from https://rdap.verisign.com/com/v1/domain/pornsheriff.com.
Nameserver terry.ns.cloudflare.com is published for pornsheriff.com in the registration record from https://rdap.verisign.com/com/v1/domain/pornsheriff.com.
DNS
pornsheriff.com has 4 address records, 5 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::4, 2a06:98c1:3121::4 |
| NS | margaret.ns.cloudflare.com, terry.ns.cloudflare.com |
| MX | aspmx.l.google.com (1) Google, alt1.aspmx.l.google.com (5) Google, alt2.aspmx.l.google.com (5) Google, alt3.aspmx.l.google.com (10) Google, alt4.aspmx.l.google.com (10) Google |
| SPF | absent |
| DMARC | absent |
| CAA | — |
| Wildcard | off |
| DNSSEC | not signed |
| Resolver | 1.1.1.1:53 |
IPv4 address 188.114.96.3 answers for pornsheriff.com at resolver 1.1.1.1:53.
IPv4 address 188.114.97.3 answers for pornsheriff.com at resolver 1.1.1.1:53.
IPv6 address 2a06:98c1:3120::4 answers for pornsheriff.com at resolver 1.1.1.1:53.
IPv6 address 2a06:98c1:3121::4 answers for pornsheriff.com at resolver 1.1.1.1:53.
Mail exchanger aspmx.l.google.com has preference 1. The host is recognised as Google.
Mail exchanger alt1.aspmx.l.google.com has preference 5. The host is recognised as Google.
Mail exchanger alt2.aspmx.l.google.com has preference 5. The host is recognised as Google.
Mail exchanger alt3.aspmx.l.google.com has preference 10. The host is recognised as Google.
Mail exchanger alt4.aspmx.l.google.com has preference 10. The host is recognised as Google.
Hosting and geo
pornsheriff.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 pornsheriff.com is valid, with 73 days left and 2 subject alternative names. Source: tls:443.
| Issuer | WE1 |
|---|---|
| Subject | pornsheriff.com |
| Valid from | 14 October 2026 |
| Valid until | 12 January 2027 |
| Days left | 73 |
| SAN count | 2 |
| Protocol | TLS 1.3 |
| Source | tls:443 |
Subject alternative names: *.pornsheriff.com, pornsheriff.com.
Tech stack
Tech detection checked the fetched homepage and named 11 products. Source: wappalyzergo.
- Age Gate · WordPress plugins
- Cloudflare · CDN
- HTTP/3 · Miscellaneous
- Modern Image Formats · WordPress plugins, Performance
- MySQL · Databases
- PHP · Programming languages
- Speculative Loading · WordPress plugins, Performance
- W3 Total Cache · Caching, WordPress plugins
- WPMU DEV Smush · WordPress plugins
- WordPress · CMS, Blogs
- Yoast SEO · SEO, WordPress plugins
Age Gate is filed under WordPress plugins.
Cloudflare is filed under CDN.
HTTP/3 is filed under Miscellaneous.
Modern Image Formats is filed under WordPress plugins, Performance.
MySQL is filed under Databases.
PHP is filed under Programming languages.
Speculative Loading is filed under WordPress plugins, Performance.
W3 Total Cache is filed under Caching, WordPress plugins.
WPMU DEV Smush is filed under WordPress plugins.
WordPress is filed under CMS, Blogs.
Yoast SEO is filed under SEO, WordPress plugins.
On-page checks
The homepage returned HTTP 200 in 1977 ms. The target title is 64 characters and the page has 1 H1 heading.
| Status | 200 |
|---|---|
| TTFB | 1977 ms |
| Title length | 64 no |
| Quoted title | "PornSheriff - Best Porn Sites & Free Adult WebSites List In 2026" |
| Meta description | "PornSheriff brings you the best porn sites of 2026. Watch free porn videos, Enjoy premium XXX movies all from the most popular sites online." 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://pornsheriff.com/ |
| Language | en-US |
| Links | 1377 |
| Images | 3 |
| 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 pornsheriff.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 pornsheriff.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
- October 2026: dns aaaa changed from 2a06:98c1:3120::3,2a06:98c1:3121::3 to 2a06:98c1:3120::4,2a06:98c1:3121::4.
Questions
Is pornsheriff.com safe?
Cloudflare family DNS returned a block for pornsheriff.com. That resolver covers adult and malware names.
Who hosts pornsheriff.com?
pornsheriff.com is placed in Toronto, Canada.
When does pornsheriff.com expire?
pornsheriff.com expires on 8 October 2029 according to https://rdap.verisign.com/com/v1/domain/pornsheriff.com.
Who owns pornsheriff.com?
The registry did not return a person or a company for pornsheriff.com. RDAP often redacts the registrant. The registrar on file is 123-Reg Limited.
Sources
- RDAP source https://rdap.verisign.com/com/v1/domain/pornsheriff.com at 2026-10-30T14:10:11Z
- DNS source 1.1.1.1:53 at 2026-10-30T14:10:11Z
- TLS source tls:443 at 2026-10-30T14:10:11Z
- HTTP source https://pornsheriff.com/ at 2026-10-30T14:10:11Z
- Tech source wappalyzergo at 2026-10-30T14:10:11Z
- Geo source db-ip at 2026-10-30T14:10:11Z
- Safety source family DNS and local lists at 2026-10-30T14:10:11Z
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.