vtbe.to

Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .

Online · 200SafeSSL: 82 days left3 years oldTranco #396481

One re-check per domain each UTC day.

65

vtbe.to was registered on 29 Jul 2023 via NAMECHEAP and the registry expiry is 29 Jul 2027. WHOIS data came from RDAP at https://rdap.tonicregistry.to/rdap/domain/vtbe.to.

vtbe.to publishes 2 nameservers. DNSSEC is not signed.

vtbe.to has 2 IPv4 addresses (104.21.25.141, 172.67.134.75) and 2 IPv6 addresses (2606:4700:3033::6815:198d, 2606:4700:3037::ac43:864b). The geolocation database places 104.21.25.141 in Toronto, Canada.

The TLS certificate from WE1 is valid and has 82 days left (TLS 1.3). The homepage answered HTTP 200.

Tech detection named Bootstrap, Cloudflare, Google Analytics, HTTP/3 and Typed.js. The fingerprints ran on the homepage that was already downloaded.

No safety warning was recorded for vtbe.to in the checks that ran.

Domain · RDAP/WHOIS

vtbe.to was registered on 29 Jul 2023 via NAMECHEAP. The registry returned 1 status value and 2 nameservers from https://rdap.tonicregistry.to/rdap/domain/vtbe.to.

Registeredsince 29 Jul 2023
Created29 July 2023
Updated10 July 2026
Expires29 July 2027
RegistrarNAMECHEAP
Statusactive
Nameserversaudrey.ns.cloudflare.com, kellen.ns.cloudflare.com
DNSSECno
Sourcehttps://rdap.tonicregistry.to/rdap/domain/vtbe.to

Nameserver audrey.ns.cloudflare.com is published for vtbe.to in the registration record from https://rdap.tonicregistry.to/rdap/domain/vtbe.to.

Nameserver kellen.ns.cloudflare.com is published for vtbe.to in the registration record from https://rdap.tonicregistry.to/rdap/domain/vtbe.to.

DNS

vtbe.to has 4 address records, 0 mail exchangers and 2 nameservers, measured at 1.1.1.1:53.

A104.21.25.141, 172.67.134.75
AAAA2606:4700:3033::6815:198d, 2606:4700:3037::ac43:864b
NSaudrey.ns.cloudflare.com, kellen.ns.cloudflare.com
MX—
SPFabsent
DMARCabsent
CAA—
Wildcardoff
DNSSECnot signed
Resolver1.1.1.1:53

IPv4 address 104.21.25.141 answers for vtbe.to at resolver 1.1.1.1:53.

IPv4 address 172.67.134.75 answers for vtbe.to at resolver 1.1.1.1:53.

IPv6 address 2606:4700:3033::6815:198d answers for vtbe.to at resolver 1.1.1.1:53.

IPv6 address 2606:4700:3037::ac43:864b answers for vtbe.to at resolver 1.1.1.1:53.

Hosting and geo

vtbe.to is placed in Toronto, Canada by the local geolocation database (db-ip).

Address104.21.25.141
CountryCanada
CityToronto
Sourcedb-ip

IP geolocation by DB-IP

SSL/TLS

The certificate for vtbe.to is valid, with 82 days left and 2 subject alternative names. Source: tls:443.

IssuerWE1
Subjectvtbe.to
Valid from24 October 2026
Valid until22 January 2027
Days left82
SAN count2
ProtocolTLS 1.3
Sourcetls:443

Subject alternative names: *.vtbe.to, vtbe.to.

Tech stack

Tech detection checked the fetched homepage and named 5 products. Source: wappalyzergo.

  • Bootstrap · UI frameworks
  • Cloudflare · CDN
  • Google Analytics · Analytics
  • HTTP/3 · Miscellaneous
  • Typed.js · JavaScript libraries

Bootstrap is filed under UI frameworks.

Cloudflare is filed under CDN.

Google Analytics is filed under Analytics.

HTTP/3 is filed under Miscellaneous.

Typed.js is filed under JavaScript libraries.

On-page checks

The homepage returned HTTP 200 in 62 ms. The target title is 30 characters and the page has 1 H1 heading.

Status200
TTFB62 ms
Title length30 yes
Quoted title"vTube - Video Hosting Platform"
Meta description"vTube is a secure cloud storage solution for sharing personal videos. You can get access to your videos super fast on any device & platform across the world." yes
H1 count1
HSTSno no
CSPno
X-Frame-Options—
Robots meta—
Canonical—
Languageen
Links6
Images4
Faviconyes

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 vtbe.to is clear, and URLhaus is clear. Source: family DNS and local lists.

Family DNSclear
URLhausclear
UT1—
Web Risknot run
Sourcefamily DNS and local lists
HSTSno
CSPno

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 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 vtbe.to 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 vtbe.to?

vtbe.to is placed in Toronto, Canada.

When does vtbe.to expire?

vtbe.to expires on 29 July 2027 according to https://rdap.tonicregistry.to/rdap/domain/vtbe.to.

Who owns vtbe.to?

The registry did not return a person or a company for vtbe.to. RDAP often redacts the registrant. The registrar on file is NAMECHEAP.

Sources

  • RDAP source https://rdap.tonicregistry.to/rdap/domain/vtbe.to at 2026-10-30T15:18:52Z
  • DNS source 1.1.1.1:53 at 2026-10-30T15:18:52Z
  • TLS source tls:443 at 2026-10-30T15:18:52Z
  • HTTP source https://vtbe.to/ at 2026-10-30T15:18:52Z
  • Tech source wappalyzergo at 2026-10-30T15:18:52Z
  • Geo source db-ip at 2026-10-30T15:18:52Z
  • Safety source family DNS and local lists at 2026-10-30T15:18:52Z

Methodology

Related reports

No other indexable reports share this TLD, host, or registrar yet.

.to NAMECHEAP

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.

Removal policy

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.