javabc.com
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
OfflineFamily DNS blockedSSL: 69 days left10 years old
45
javabc.com was registered on 17 Dec 2015 via NameSilo, LLC and the registry expiry is 17 Dec 2026. WHOIS data came from RDAP at https://rdap.verisign.com/com/v1/domain/javabc.com.
javabc.com publishes 2 nameservers. DNSSEC is not signed.
javabc.com has 2 IPv4 addresses (104.21.4.75, 172.67.131.197) and 2 IPv6 addresses (2606:4700:3033::ac43:83c5, 2606:4700:3036::6815:44b). The geolocation database places 104.21.4.75 in Toronto, Canada.
The TLS certificate from WE1 is valid and has 69 days left (TLS 1.3).
Domain · RDAP/WHOIS
javabc.com was registered on 17 Dec 2015 via NameSilo, LLC. The registry returned 1 status value and 2 nameservers from https://rdap.verisign.com/com/v1/domain/javabc.com.
| Registered | since 17 Dec 2015 |
|---|---|
| Created | 17 December 2015 |
| Updated | 12 August 2026 |
| Expires | 17 December 2026 |
| Registrar | NameSilo, LLC |
| Status | client transfer prohibited |
| Nameservers | felicity.ns.cloudflare.com, vida.ns.cloudflare.com |
| DNSSEC | no |
| Source | https://rdap.verisign.com/com/v1/domain/javabc.com |
javabc.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 felicity.ns.cloudflare.com is published for javabc.com in the registration record from https://rdap.verisign.com/com/v1/domain/javabc.com.
Nameserver vida.ns.cloudflare.com is published for javabc.com in the registration record from https://rdap.verisign.com/com/v1/domain/javabc.com.
DNS
javabc.com has 4 address records, 1 mail exchanger and 2 nameservers, measured at 1.1.1.1:53.
| A | 104.21.4.75, 172.67.131.197 |
|---|---|
| AAAA | 2606:4700:3033::ac43:83c5, 2606:4700:3036::6815:44b |
| NS | felicity.ns.cloudflare.com, vida.ns.cloudflare.com |
| MX | mail.javabc.com (0) |
| SPF | present |
| DMARC | present |
| CAA | — |
| Wildcard | on |
| DNSSEC | not signed |
| Resolver | 1.1.1.1:53 |
The SPF text record at javabc.com is "v=spf1 mx a +all".
The DMARC text record at _dmarc.javabc.com is "v=DMARC1; p=reject; rua=mailto:[email protected]".
IPv4 address 104.21.4.75 answers for javabc.com at resolver 1.1.1.1:53.
IPv4 address 172.67.131.197 answers for javabc.com at resolver 1.1.1.1:53.
IPv6 address 2606:4700:3033::ac43:83c5 answers for javabc.com at resolver 1.1.1.1:53.
IPv6 address 2606:4700:3036::6815:44b answers for javabc.com at resolver 1.1.1.1:53.
Mail exchanger mail.javabc.com has preference 0.
A random label under javabc.com also resolved, which means wildcard DNS is on.
Hosting and geo
javabc.com is placed in Toronto, Canada by the local geolocation database (db-ip).
| Address | 104.21.4.75 |
|---|---|
| Country | Canada |
| City | Toronto |
| Source | db-ip |
SSL/TLS
The certificate for javabc.com is valid, with 69 days left and 2 subject alternative names. Source: tls:443.
| Issuer | WE1 |
|---|---|
| Subject | javabc.com |
| Valid from | 10 October 2026 |
| Valid until | 8 January 2027 |
| Days left | 69 |
| SAN count | 2 |
| Protocol | TLS 1.3 |
| Source | tls:443 |
Subject alternative names: *.javabc.com, javabc.com.
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 |
|---|
context deadline exceeded
Security
Family DNS for javabc.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 javabc.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 20 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
First checked on 30 October 2026; changes will appear here.
Questions
Is javabc.com safe?
Cloudflare family DNS returned a block for javabc.com. That resolver covers adult and malware names.
Who hosts javabc.com?
javabc.com is placed in Toronto, Canada.
When does javabc.com expire?
javabc.com expires on 17 December 2026 according to https://rdap.verisign.com/com/v1/domain/javabc.com.
Who owns javabc.com?
The registry did not return a person or a company for javabc.com. RDAP often redacts the registrant. The registrar on file is NameSilo, LLC.
Sources
- RDAP source https://rdap.verisign.com/com/v1/domain/javabc.com at 2026-10-30T13:59:51Z
- DNS source 1.1.1.1:53 at 2026-10-30T13:59:51Z
- TLS source tls:443 at 2026-10-30T13:59:51Z
- HTTP source https://javabc.com/ at 2026-10-30T13:59:51Z
- Tech source not available at 2026-10-30T13:59:51Z
- Geo source db-ip at 2026-10-30T13:59:51Z
- Safety source family DNS and local lists at 2026-10-30T13:59:51Z
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.