findtubes.com
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
75
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
75
findtubes.com was registered on 12 Dec 2007 via EuroDNS S.A. and the registry expiry is 12 Dec 2031. WHOIS data came from RDAP at https://rdap.verisign.com/com/v1/domain/findtubes.com.
findtubes.com publishes 2 nameservers. DNSSEC is not signed.
findtubes.com has 2 IPv4 addresses (104.18.6.200, 104.18.7.200) and 2 IPv6 addresses (2606:4700::6812:6c8, 2606:4700::6812:7c8). The geolocation database places 104.18.6.200 in Toronto, Canada.
The TLS certificate from WE1 is valid and has 80 days left (TLS 1.3). The homepage answered HTTP 200.
Tech detection named Cloudflare and HSTS. The fingerprints ran on the homepage that was already downloaded.
findtubes.com was registered on 12 Dec 2007 via EuroDNS S.A.. The registry returned 1 status value and 2 nameservers from https://rdap.verisign.com/com/v1/domain/findtubes.com.
| Registered | since 12 Dec 2007 |
|---|---|
| Created | 12 December 2007 |
| Updated | 13 December 2024 |
| Expires | 12 December 2031 |
| Registrar | EuroDNS S.A. |
| Status | client transfer prohibited |
| Nameservers | deb.ns.cloudflare.com, venkat.ns.cloudflare.com |
| DNSSEC | no |
| Source | https://rdap.verisign.com/com/v1/domain/findtubes.com |
findtubes.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 deb.ns.cloudflare.com is published for findtubes.com in the registration record from https://rdap.verisign.com/com/v1/domain/findtubes.com.
Nameserver venkat.ns.cloudflare.com is published for findtubes.com in the registration record from https://rdap.verisign.com/com/v1/domain/findtubes.com.
findtubes.com has 4 address records, 0 mail exchangers and 2 nameservers, measured at 1.1.1.1:53.
| A | 104.18.6.200, 104.18.7.200 |
|---|---|
| AAAA | 2606:4700::6812:6c8, 2606:4700::6812:7c8 |
| NS | deb.ns.cloudflare.com, venkat.ns.cloudflare.com |
| MX | — |
| SPF | present |
| DMARC | present |
| CAA | — |
| Wildcard | off |
| DNSSEC | not signed |
| Resolver | 1.1.1.1:53 |
The SPF text record at findtubes.com is "v=spf1 -all".
The DMARC text record at _dmarc.findtubes.com is "v=DMARC1; p=reject; pct=100".
IPv4 address 104.18.6.200 answers for findtubes.com at resolver 1.1.1.1:53.
IPv4 address 104.18.7.200 answers for findtubes.com at resolver 1.1.1.1:53.
IPv6 address 2606:4700::6812:6c8 answers for findtubes.com at resolver 1.1.1.1:53.
IPv6 address 2606:4700::6812:7c8 answers for findtubes.com at resolver 1.1.1.1:53.
findtubes.com is placed in Toronto, Canada by the local geolocation database (db-ip).
| Address | 104.18.6.200 |
|---|---|
| Country | Canada |
| City | Toronto |
| Source | db-ip |
The certificate for findtubes.com is valid, with 80 days left and 2 subject alternative names. Source: tls:443.
| Issuer | WE1 |
|---|---|
| Subject | findtubes.com |
| Valid from | 21 October 2026 |
| Valid until | 19 January 2027 |
| Days left | 80 |
| SAN count | 2 |
| Protocol | TLS 1.3 |
| Source | tls:443 |
Subject alternative names: *.findtubes.com, findtubes.com.
Tech detection checked the fetched homepage and named 2 products. Source: wappalyzergo.
Cloudflare is filed under CDN.
HSTS is filed under Security.
The homepage returned HTTP 200 in 18 ms. The target title is 41 characters and the page has 0 H1 headings.
| Status | 200 |
|---|---|
| TTFB | 18 ms |
| Title length | 41 yes |
| Quoted title | "Free Porn Tube Search Engine - Find Tubes" |
| Meta description | "Easily search through 76,002,991 porn videos at FindTubes. Find the best porn now!" yes |
| H1 count | 0 |
| HSTS | yes yes |
| CSP | yes |
| X-Frame-Options | DENY |
| Robots meta | — |
| Canonical | https://www.findtubes.com/ |
| Language | en |
| Links | 21 |
| Images | 6 |
| 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 findtubes.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 | yes |
| CSP | yes |
Cloudflare family DNS returned a block for findtubes.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 10 of 20. SPF, DMARC, CAA, and DNSSEC are five points each.
Security headers 15 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 findtubes.com. That resolver covers adult and malware names.
findtubes.com is placed in Toronto, Canada.
findtubes.com expires on 12 December 2031 according to https://rdap.verisign.com/com/v1/domain/findtubes.com.
The registry did not return a person or a company for findtubes.com. RDAP often redacts the registrant. The registrar on file is EuroDNS S.A..
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.