reachporn.com
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
65
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
65
reachporn.com was registered on 29 Oct 2017 via GoDaddy.com, LLC and the registry expiry is 29 Oct 2027. WHOIS data came from RDAP at https://rdap.verisign.com/com/v1/domain/reachporn.com.
reachporn.com publishes 2 nameservers. DNSSEC is not signed.
reachporn.com has 3 IPv4 addresses (104.26.10.205, 104.26.11.205, 172.67.68.221) and 3 IPv6 addresses (2606:4700:20::681a:acd, 2606:4700:20::681a:bcd, 2606:4700:20::ac43:44dd). The geolocation database places 104.26.10.205 in Toronto, Canada.
The TLS certificate from WE1 is valid and has 81 days left (TLS 1.3). The homepage answered HTTP 200.
Tech detection named Cloudflare, HTTP/3, MySQL, PHP, W3 Total Cache and WordPress. The fingerprints ran on the homepage that was already downloaded.
reachporn.com was registered on 29 Oct 2017 via GoDaddy.com, LLC. The registry returned 4 status values and 2 nameservers from https://rdap.verisign.com/com/v1/domain/reachporn.com.
| Registered | since 29 Oct 2017 |
|---|---|
| Created | 29 October 2017 |
| Updated | 1 October 2026 |
| Expires | 29 October 2027 |
| Registrar | GoDaddy.com, LLC |
| Status | client delete prohibited, client renew prohibited, client transfer prohibited, client update prohibited |
| Nameservers | ben.ns.cloudflare.com, jade.ns.cloudflare.com |
| DNSSEC | no |
| Source | https://rdap.verisign.com/com/v1/domain/reachporn.com |
reachporn.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.
reachporn.com carries the status "client renew prohibited". The registrar has asked the registry to refuse a renewal. The expiry date still stands until a different status is set.
reachporn.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.
reachporn.com carries the status "client update prohibited". The registrar has asked the registry to refuse updates to the domain object. Contact and nameserver changes wait until the lock is lifted by the registrar of record.
Nameserver ben.ns.cloudflare.com is published for reachporn.com in the registration record from https://rdap.verisign.com/com/v1/domain/reachporn.com.
Nameserver jade.ns.cloudflare.com is published for reachporn.com in the registration record from https://rdap.verisign.com/com/v1/domain/reachporn.com.
reachporn.com has 6 address records, 1 mail exchanger and 2 nameservers, measured at 1.1.1.1:53.
| A | 104.26.10.205, 104.26.11.205, 172.67.68.221 |
|---|---|
| AAAA | 2606:4700:20::681a:acd, 2606:4700:20::681a:bcd, 2606:4700:20::ac43:44dd |
| NS | ben.ns.cloudflare.com, jade.ns.cloudflare.com |
| MX | reachporn-com.mail.protection.outlook.com (0) Microsoft 365 |
| SPF | present |
| DMARC | present |
| CAA | issue comodoca.com, issue digicert.com; cansignhttpexchanges=yes, issue letsencrypt.org, issue pki.goog; cansignhttpexchanges=yes, issue ssl.com, issuewild comodoca.com, issuewild digicert.com; cansignhttpexchanges=yes, issuewild letsencrypt.org, issuewild pki.goog; cansignhttpexchanges=yes, issuewild ssl.com |
| Wildcard | on |
| DNSSEC | not signed |
| Resolver | 1.1.1.1:53 |
The SPF text record at reachporn.com is "v=spf1 include:spf.protection.outlook.com mx ip4:116.202.241.215 -all".
The DMARC text record at _dmarc.reachporn.com is "v=DMARC1; p=none; rua=mailto:[email protected]".
IPv4 address 104.26.10.205 answers for reachporn.com at resolver 1.1.1.1:53.
IPv4 address 104.26.11.205 answers for reachporn.com at resolver 1.1.1.1:53.
IPv4 address 172.67.68.221 answers for reachporn.com at resolver 1.1.1.1:53.
IPv6 address 2606:4700:20::681a:acd answers for reachporn.com at resolver 1.1.1.1:53.
IPv6 address 2606:4700:20::681a:bcd answers for reachporn.com at resolver 1.1.1.1:53.
IPv6 address 2606:4700:20::ac43:44dd answers for reachporn.com at resolver 1.1.1.1:53.
Mail exchanger reachporn-com.mail.protection.outlook.com has preference 0. The host is recognised as Microsoft 365.
A random label under reachporn.com also resolved, which means wildcard DNS is on.
reachporn.com is placed in Toronto, Canada by the local geolocation database (db-ip).
| Address | 104.26.10.205 |
|---|---|
| Country | Canada |
| City | Toronto |
| Source | db-ip |
The certificate for reachporn.com is valid, with 81 days left and 2 subject alternative names. Source: tls:443.
| Issuer | WE1 |
|---|---|
| Subject | reachporn.com |
| Valid from | 23 October 2026 |
| Valid until | 21 January 2027 |
| Days left | 81 |
| SAN count | 2 |
| Protocol | TLS 1.3 |
| Source | tls:443 |
Subject alternative names: *.reachporn.com, reachporn.com.
Tech detection checked the fetched homepage and named 6 products. Source: wappalyzergo.
Cloudflare is filed under CDN.
HTTP/3 is filed under Miscellaneous.
MySQL is filed under Databases.
PHP is filed under Programming languages.
W3 Total Cache is filed under Caching, WordPress plugins.
WordPress is filed under CMS, Blogs.
The homepage returned HTTP 200 in 69 ms. The target title is 61 characters and the page has 2 H1 headings.
| Status | 200 |
|---|---|
| TTFB | 69 ms |
| Title length | 61 no |
| Quoted title | "Reach Porn - List Of The Best Porn Sites & Free Porn of 2026!" |
| Meta description | "Reach the best porn sites on the Net. List and reviews of free and premium porn sites, all organized by categories and ordered by quality." yes |
| H1 count | 2 |
| 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://reachporn.com/ |
| Language | en-US |
| Links | 2025 |
| 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.
Family DNS for reachporn.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 reachporn.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.
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 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.
First checked on 30 October 2026; changes will appear here.
Cloudflare family DNS returned a block for reachporn.com. That resolver covers adult and malware names.
reachporn.com is placed in Toronto, Canada.
reachporn.com expires on 29 October 2027 according to https://rdap.verisign.com/com/v1/domain/reachporn.com.
The registry did not return a person or a company for reachporn.com. RDAP often redacts the registrant. The registrar on file is GoDaddy.com, LLC.
No other indexable reports share this TLD, host, or registrar yet.
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.
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.