tube3.com
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
OfflineFamily DNS blockedSSL: 35 days left19 years oldTranco #52856
25
tube3.com was registered on 13 Jan 2007 via Sea Wasp, LLC and the registry expiry is 13 Jan 2027. WHOIS data came from RDAP at https://rdap.verisign.com/com/v1/domain/tube3.com.
tube3.com publishes 2 nameservers. DNSSEC is not signed.
tube3.com has 1 IPv4 address (31.220.27.57) and 1 IPv6 address (2a02:b4a:1:3:5607::1). The geolocation database places 31.220.27.57 in Amsterdam, The Netherlands.
The TLS certificate from YR2 is not valid (TLS 1.2).
Domain · RDAP/WHOIS
tube3.com was registered on 13 Jan 2007 via Sea Wasp, LLC. The registry returned 3 status values and 2 nameservers from https://rdap.verisign.com/com/v1/domain/tube3.com.
| Registered | since 13 Jan 2007 |
|---|---|
| Created | 13 January 2007 |
| Updated | 30 December 2025 |
| Expires | 13 January 2027 |
| Registrar | Sea Wasp, LLC |
| Status | client delete prohibited, client transfer prohibited, client update prohibited |
| Nameservers | ns1.tube3.com, ns2.tube3.com |
| DNSSEC | no |
| Source | https://rdap.verisign.com/com/v1/domain/tube3.com |
tube3.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.
tube3.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.
tube3.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 ns1.tube3.com is published for tube3.com in the registration record from https://rdap.verisign.com/com/v1/domain/tube3.com.
Nameserver ns2.tube3.com is published for tube3.com in the registration record from https://rdap.verisign.com/com/v1/domain/tube3.com.
DNS
tube3.com has 2 address records, 1 mail exchanger and 2 nameservers, measured at 1.1.1.1:53.
| A | 31.220.27.57 |
|---|---|
| AAAA | 2a02:b4a:1:3:5607::1 |
| NS | ns1.tube3.com, ns2.tube3.com |
| MX | tube3.com (10) |
| SPF | present |
| DMARC | present |
| CAA | — |
| Wildcard | on |
| DNSSEC | not signed |
| Resolver | 1.1.1.1:53 |
The SPF text record at tube3.com is "v=spf1 ip4:31.220.27.57/32 ~all".
The DMARC text record at _dmarc.tube3.com is "v=DMARC1; p=none; rua=mailto:[email protected]".
IPv4 address 31.220.27.57 answers for tube3.com at resolver 1.1.1.1:53.
IPv6 address 2a02:b4a:1:3:5607::1 answers for tube3.com at resolver 1.1.1.1:53.
Mail exchanger tube3.com has preference 10.
A random label under tube3.com also resolved, which means wildcard DNS is on.
Hosting and geo
tube3.com is placed in Amsterdam, The Netherlands by the local geolocation database (db-ip).
| Address | 31.220.27.57 |
|---|---|
| Country | The Netherlands |
| City | Amsterdam |
| Source | db-ip |
SSL/TLS
The certificate for tube3.com is not valid, with 35 days left and 2 subject alternative names. Source: tls:443.
| Issuer | YR2 |
|---|---|
| Subject | 2tube.com |
| Valid from | 7 September 2026 |
| Valid until | 6 December 2026 |
| Days left | 35 |
| SAN count | 2 |
| Protocol | TLS 1.2 |
| Source | tls:443 |
Subject alternative names: 2tube.com, www.2tube.com.
Validation result: certificate did not validate
Tech stack
Tech detection did not run.
| Checked | no |
|---|---|
| Source | wappalyzergo |
On-page checks
The homepage fetch did not return a status code.
| Status | none |
|---|
Get "https://tube3.com/": tls: failed to verify certificate: x509: certificate is valid for 2tube.com, www.2tube.com, not tube3.com
Security
Family DNS for tube3.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 tube3.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 10 of 25. DNS answer plus a homepage status in the 2xx or 3xx range.
TLS 0 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
- October 2026: geo city changed from empty to Amsterdam.
- October 2026: geo country changed from empty to The Netherlands.
Questions
Is tube3.com safe?
Cloudflare family DNS returned a block for tube3.com. That resolver covers adult and malware names.
Who hosts tube3.com?
tube3.com is placed in Amsterdam, The Netherlands.
When does tube3.com expire?
tube3.com expires on 13 January 2027 according to https://rdap.verisign.com/com/v1/domain/tube3.com.
Who owns tube3.com?
The registry did not return a person or a company for tube3.com. RDAP often redacts the registrant. The registrar on file is Sea Wasp, LLC.
Sources
- RDAP source https://rdap.verisign.com/com/v1/domain/tube3.com at 2026-10-30T14:17:54Z
- DNS source 1.1.1.1:53 at 2026-10-30T14:17:54Z
- TLS source tls:443 at 2026-10-30T14:17:54Z
- HTTP source https://tube3.com/ at 2026-10-30T14:17:54Z
- Tech source not available at 2026-10-30T14:17:54Z
- Geo source db-ip at 2026-10-30T14:17:54Z
- Safety source family DNS and local lists at 2026-10-30T14:17:54Z
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.