v2-based.app is registered with domain: APP. Its SSL certificate from Google Trust Services expired on 5 Jul 2025.
What security vendors and the WOT community say about this domain.
What loads and tracks visitors when the homepage opens.
Running a full browser scan of the homepage… This takes about a minute.
No similar domains registered in the last 90 days.
From CubDomain's daily newly registered domains. Similar doesn't mean malicious.
Is v2-based.app’s name taken on other extensions?
Every IP address v2-based.app resolves to, and where it's hosted.
| Host | IPv4 address | TTL |
|---|---|---|
| v2-based.app | 104.21.59.134 | 300 |
| v2-based.app | 172.67.177.234 | 300 |
| Host | IPv6 address | TTL |
|---|---|---|
| v2-based.app | 2606:4700:3030::6815:3b86 | 300 |
| v2-based.app | 2606:4700:3037::ac43:b1ea | 300 |
| Host | Name server | TTL |
|---|---|---|
| v2-based.app | alaric.ns.cloudflare.com | 21600 |
| v2-based.app | rosalyn.ns.cloudflare.com | 21600 |
| Host | Start of authority | TTL |
|---|---|---|
| v2-based.app | alaric.ns.cloudflare.com dns.cloudflare.com 2371746542 10000 2400 604800 1800 | 1800 |
Other domains served from 104.21.59.134. Normal for shared hosting and CDNs.
No reviews yet. Used v2-based.app? Be the first to say how it went.
Reviews are from CubDomain users and are separate from the security verdicts above.
Common questions, answered from this report's data.
v2-based.app has no community safety rating yet. Its SSL certificate expired on 5 Jul 2025. See Security →
v2-based.app is registered through domain: APP. See Overview →
v2-based.app is served from 2 IP addresses, mainly on AS13335. See Hosting →
Four timed TCP connections to port 443 from CubDomain's servers.
CubDomain is not affiliated with v2-based.app. Data is collected independently from public sources and some figures are estimates, provided for information only.
Spam and malware blocklists for the site's IP and mail servers.
When the site first appeared, and what has changed since.
We record what changes from the next time this report is refreshed.
Found in public certificate transparency logs.
Searching the certificate transparency logs… This can take up to a minute.