Report ID: #836F3F37

jbl.es

United States Valid HTTPS Updated
70
Safe
AddressFortify · jbl.es — Report card
AddressFortify · jbl.es

What we know about jbl.es

Whether you are vetting jbl.es for a transaction, a partnership or simple curiosity, the public-record summary below will save you a few searches.

Technical Information

IP Address199.27.116.77
Server LocationUnited States · Addison
ISP / ProviderUnknown
SSL Certificate Valid HTTPS
SSL IssuerSectigo RSA Organization Validation Secure Server CA
Valid Until2026-08-12
RegistrarUnknown

Initial findings

Our automated probe of jbl.es returned a clean DNS answer pointing to United States, served by Unknown, with the TLS handshake responding OK.

HTTPS verdict

Our HTTPS probe to jbl.es concluded with: OK. Together with the registrar and hosting country, this forms the security side of the scorecard.

Registration history

jbl.es has existed for about ? years. Long-lived domains are usually associated with established projects, although age alone is not a guarantee of safety.

Where the data lives

Anything you submit to jbl.es is processed on servers located in United States. Choose to share data accordingly.

Risk perspective

Domains with the profile of jbl.es (age ? years, SSL OK, registrar Unknown, country United States) usually fall in the "safe" category in our automated scoring.

Verdict

Trust score: 70/100safe. This is an automated, technical-only verdict; treat it as one data point among many.

What looks good

  • Hosting on an established ISP network
  • Consistent A and AAAA records
  • Subject Alternative Names cover the domain correctly
  • Stable IPv4 hosting

What to watch

  • Recently registered domain
  • No structured Schema.org metadata published
  • Hosting on a residential/dynamic IP block

Frequently Asked Questions

Is jbl.es on a security blocklist?
No automatic blocklist hits were registered for jbl.es during this check. Refresh the report to recheck.
Is jbl.es a phishing website?
Our scanner does not perform visual similarity checks. We can only confirm that no obvious infrastructure markers (cert mismatch, fresh registration with high traffic) were triggered.
What looks risky about jbl.es?
For jbl.es we look at: age ? yrs, SSL OK, registrar Unknown and hosting in United States. Any single weak point can drag the technical confidence down.
How often is jbl.es re-checked?
By default the report is refreshed every 30 days, plus on every manual re-check from the dashboard.
Is the score enough to decide?
A high score is necessary but not sufficient. Always pair the report with a content-level sanity check before transacting.

This report is generated automatically from public technical signals. It is not legal or financial advice.

Vet your next domain in under 10 seconds.

No signup. No credit card. No hidden quotas.

Start a free check →