thejavasea.com
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
80
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
80
thejavasea.com was registered on 8 May 2004 via Moniker Online Services LLC and the registry expiry is 8 May 2027. WHOIS data came from RDAP at https://rdap.verisign.com/com/v1/domain/thejavasea.com.
thejavasea.com publishes 2 nameservers. DNSSEC is not signed.
thejavasea.com has 2 IPv4 addresses (104.21.93.226, 172.67.216.82) and 2 IPv6 addresses (2606:4700:3033::ac43:d852, 2606:4700:3036::6815:5de2). The geolocation database places 104.21.93.226 in Toronto, Canada.
The TLS certificate from WE1 is valid and has 38 days left (TLS 1.3). The homepage answered HTTP 302.
No safety warning was recorded for thejavasea.com in the checks that ran.
thejavasea.com was registered on 8 May 2004 via Moniker Online Services LLC. The registry returned 1 status value and 2 nameservers from https://rdap.verisign.com/com/v1/domain/thejavasea.com.
| Registered | since 8 May 2004 |
|---|---|
| Created | 8 May 2004 |
| Updated | 1 April 2026 |
| Expires | 8 May 2027 |
| Registrar | Moniker Online Services LLC |
| Status | client transfer prohibited |
| Nameservers | pedro.ns.cloudflare.com, stephane.ns.cloudflare.com |
| DNSSEC | no |
| Source | https://rdap.verisign.com/com/v1/domain/thejavasea.com |
thejavasea.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 pedro.ns.cloudflare.com is published for thejavasea.com in the registration record from https://rdap.verisign.com/com/v1/domain/thejavasea.com.
Nameserver stephane.ns.cloudflare.com is published for thejavasea.com in the registration record from https://rdap.verisign.com/com/v1/domain/thejavasea.com.
thejavasea.com has 4 address records, 3 mail exchangers and 2 nameservers, measured at 1.1.1.1:53.
| A | 104.21.93.226, 172.67.216.82 |
|---|---|
| AAAA | 2606:4700:3033::ac43:d852, 2606:4700:3036::6815:5de2 |
| NS | pedro.ns.cloudflare.com, stephane.ns.cloudflare.com |
| MX | route2.mx.cloudflare.net (59), route3.mx.cloudflare.net (59), route1.mx.cloudflare.net (73) |
| SPF | present |
| DMARC | present |
| CAA | issue comodoca.com, issue digicert.com; cansignhttpexchanges=yes, issue letsencrypt.org, issue pki.goog; cansignhttpexchanges=yes, issue ssl.com, issuewild comodoca.com, issuewild digicert.com; cansignhttpexchanges=yes, issuewild letsencrypt.org, issuewild pki.goog; cansignhttpexchanges=yes, issuewild ssl.com |
| Wildcard | off |
| DNSSEC | not signed |
| Resolver | 1.1.1.1:53 |
The SPF text record at thejavasea.com is "v=spf1 include:_spf.mx.cloudflare.net ~all".
The DMARC text record at _dmarc.thejavasea.com is "v=DMARC1; p=none; rua=mailto:[email protected]".
IPv4 address 104.21.93.226 answers for thejavasea.com at resolver 1.1.1.1:53.
IPv4 address 172.67.216.82 answers for thejavasea.com at resolver 1.1.1.1:53.
IPv6 address 2606:4700:3033::ac43:d852 answers for thejavasea.com at resolver 1.1.1.1:53.
IPv6 address 2606:4700:3036::6815:5de2 answers for thejavasea.com at resolver 1.1.1.1:53.
Mail exchanger route2.mx.cloudflare.net has preference 59.
Mail exchanger route3.mx.cloudflare.net has preference 59.
Mail exchanger route1.mx.cloudflare.net has preference 73.
thejavasea.com is placed in Toronto, Canada by the local geolocation database (db-ip).
| Address | 104.21.93.226 |
|---|---|
| Country | Canada |
| City | Toronto |
| Source | db-ip |
The certificate for thejavasea.com is valid, with 38 days left and 2 subject alternative names. Source: tls:443.
| Issuer | WE1 |
|---|---|
| Subject | thejavasea.com |
| Valid from | 10 September 2026 |
| Valid until | 9 December 2026 |
| Days left | 38 |
| SAN count | 2 |
| Protocol | TLS 1.3 |
| Source | tls:443 |
Subject alternative names: *.thejavasea.com, thejavasea.com.
Tech detection checked the fetched homepage and named 0 products. Source: wappalyzergo.
The fingerprint set matched no product. That is a result, not a skipped check.
The homepage returned HTTP 302 in 34 ms. The target title is 28 characters and the page has 1 H1 heading.
| Status | 302 |
|---|---|
| TTFB | 34 ms |
| Title length | 28 yes |
| Quoted title | "Browser Check - DNSProxy.org" |
| Meta description | none no |
| H1 count | 1 |
| HSTS | no no |
| CSP | no |
| X-Frame-Options | — |
| Robots meta | — |
| Canonical | — |
| Language | — |
| Links | 0 |
| 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.
Family DNS for thejavasea.com is clear, and URLhaus is clear. Source: family DNS and local lists.
| Family DNS | clear |
|---|---|
| URLhaus | clear |
| UT1 | — |
| Web Risk | not run |
| Source | family DNS and local lists |
| HSTS | no |
| CSP | no |
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 15 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.
First checked on 30 October 2026; changes will appear here.
The checks that ran did not produce a safety warning, and a score is not a promise that the site is safe.
thejavasea.com is placed in Toronto, Canada.
thejavasea.com expires on 8 May 2027 according to https://rdap.verisign.com/com/v1/domain/thejavasea.com.
The registry did not return a person or a company for thejavasea.com. RDAP often redacts the registrant. The registrar on file is Moniker Online Services LLC.
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.