javgo.to
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
HTTP 403Family DNS blockedSSL: 59 days left4 years old
40
javgo.to was registered on 6 May 2022 via NAMECHEAP and the registry expiry is 6 May 2027. WHOIS data came from RDAP at https://rdap.tonicregistry.to/rdap/domain/javgo.to.
javgo.to publishes 2 nameservers. DNSSEC is not signed.
javgo.to has 2 IPv4 addresses (104.21.56.16, 172.67.175.177) and 2 IPv6 addresses (2606:4700:3032::ac43:afb1, 2606:4700:3035::6815:3810). The geolocation database places 104.21.56.16 in Toronto, Canada.
The TLS certificate from WE1 is valid and has 59 days left (TLS 1.3).
Tech detection named Cloudflare and HTTP/3. The fingerprints ran on the homepage that was already downloaded.
Domain · RDAP/WHOIS
javgo.to was registered on 6 May 2022 via NAMECHEAP. The registry returned 1 status value and 2 nameservers from https://rdap.tonicregistry.to/rdap/domain/javgo.to.
| Registered | since 6 May 2022 |
|---|---|
| Created | 6 May 2022 |
| Updated | 10 April 2026 |
| Expires | 6 May 2027 |
| Registrar | NAMECHEAP |
| Status | active |
| Nameservers | abdullah.ns.cloudflare.com, maleah.ns.cloudflare.com |
| DNSSEC | no |
| Source | https://rdap.tonicregistry.to/rdap/domain/javgo.to |
Nameserver abdullah.ns.cloudflare.com is published for javgo.to in the registration record from https://rdap.tonicregistry.to/rdap/domain/javgo.to.
Nameserver maleah.ns.cloudflare.com is published for javgo.to in the registration record from https://rdap.tonicregistry.to/rdap/domain/javgo.to.
DNS
javgo.to has 4 address records, 0 mail exchangers and 2 nameservers, measured at 1.1.1.1:53.
| A | 104.21.56.16, 172.67.175.177 |
|---|---|
| AAAA | 2606:4700:3032::ac43:afb1, 2606:4700:3035::6815:3810 |
| NS | abdullah.ns.cloudflare.com, maleah.ns.cloudflare.com |
| MX | — |
| SPF | absent |
| DMARC | absent |
| CAA | — |
| Wildcard | on |
| DNSSEC | not signed |
| Resolver | 1.1.1.1:53 |
IPv4 address 104.21.56.16 answers for javgo.to at resolver 1.1.1.1:53.
IPv4 address 172.67.175.177 answers for javgo.to at resolver 1.1.1.1:53.
IPv6 address 2606:4700:3032::ac43:afb1 answers for javgo.to at resolver 1.1.1.1:53.
IPv6 address 2606:4700:3035::6815:3810 answers for javgo.to at resolver 1.1.1.1:53.
A random label under javgo.to also resolved, which means wildcard DNS is on.
Hosting and geo
javgo.to is placed in Toronto, Canada by the local geolocation database (db-ip).
| Address | 104.21.56.16 |
|---|---|
| Country | Canada |
| City | Toronto |
| Source | db-ip |
SSL/TLS
The certificate for javgo.to is valid, with 59 days left and 2 subject alternative names. Source: tls:443.
| Issuer | WE1 |
|---|---|
| Subject | javgo.to |
| Valid from | 30 September 2026 |
| Valid until | 29 December 2026 |
| Days left | 59 |
| SAN count | 2 |
| Protocol | TLS 1.3 |
| Source | tls:443 |
Subject alternative names: *.javgo.to, javgo.to.
Tech stack
Tech detection checked the fetched homepage and named 2 products. Source: wappalyzergo.
- Cloudflare · CDN
- HTTP/3 · Miscellaneous
Cloudflare is filed under CDN.
HTTP/3 is filed under Miscellaneous.
On-page checks
The homepage returned HTTP 403 in 43 ms. The target title is 32 characters and the page has 1 H1 heading.
| Status | 403 |
|---|---|
| TTFB | 43 ms |
| Title length | 32 yes |
| Quoted title | "Attention Required! | Cloudflare" |
| Meta description | none no |
| H1 count | 1 |
| HSTS | no no |
| CSP | no |
| X-Frame-Options | SAMEORIGIN |
| Robots meta | noindex, nofollow |
| Canonical | — |
| Language | en-US |
| Links | 1 |
| Images | 0 |
| Favicon | no |
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 javgo.to 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 javgo.to. 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 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 5 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
First checked on 30 October 2026; changes will appear here.
Questions
Is javgo.to safe?
Cloudflare family DNS returned a block for javgo.to. That resolver covers adult and malware names.
Who hosts javgo.to?
javgo.to is placed in Toronto, Canada.
When does javgo.to expire?
javgo.to expires on 6 May 2027 according to https://rdap.tonicregistry.to/rdap/domain/javgo.to.
Who owns javgo.to?
The registry did not return a person or a company for javgo.to. RDAP often redacts the registrant. The registrar on file is NAMECHEAP.
Sources
- RDAP source https://rdap.tonicregistry.to/rdap/domain/javgo.to at 2026-10-30T15:16:11Z
- DNS source 1.1.1.1:53 at 2026-10-30T15:16:11Z
- TLS source tls:443 at 2026-10-30T15:16:11Z
- HTTP source https://javgo.to/ at 2026-10-30T15:16:11Z
- Tech source wappalyzergo at 2026-10-30T15:16:11Z
- Geo source db-ip at 2026-10-30T15:16:11Z
- Safety source family DNS and local lists at 2026-10-30T15:16:11Z
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.