bailbondshq.com

Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .

OfflineSafeSSL: -192 days left6 years old

One re-check per domain each UTC day.

35

bailbondshq.com was registered on 1 Jul 2020 via NameCheap, Inc. and the registry expiry is 1 Jul 2027. WHOIS data came from RDAP at https://rdap.verisign.com/com/v1/domain/bailbondshq.com.

bailbondshq.com publishes 2 nameservers. DNSSEC is not signed.

bailbondshq.com has 1 IPv4 address (184.94.213.170). The geolocation database places 184.94.213.170 in Los Angeles (West Los Angeles), United States.

The TLS certificate from Sectigo RSA Domain Validation Secure Server CA is not valid (TLS 1.3).

No safety warning was recorded for bailbondshq.com in the checks that ran.

Domain · RDAP/WHOIS

bailbondshq.com was registered on 1 Jul 2020 via NameCheap, Inc.. The registry returned 1 status value and 2 nameservers from https://rdap.verisign.com/com/v1/domain/bailbondshq.com.

Registeredsince 1 Jul 2020
Created1 July 2020
Updated23 August 2025
Expires1 July 2027
RegistrarNameCheap, Inc.
Statusclient transfer prohibited
Nameserversdns1.namecheaphosting.com, dns2.namecheaphosting.com
DNSSECno
Sourcehttps://rdap.verisign.com/com/v1/domain/bailbondshq.com

bailbondshq.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 dns1.namecheaphosting.com is published for bailbondshq.com in the registration record from https://rdap.verisign.com/com/v1/domain/bailbondshq.com.

Nameserver dns2.namecheaphosting.com is published for bailbondshq.com in the registration record from https://rdap.verisign.com/com/v1/domain/bailbondshq.com.

DNS

bailbondshq.com has 1 address record, 3 mail exchangers and 2 nameservers, measured at 1.1.1.1:53.

A184.94.213.170
AAAA—
NSdns1.namecheaphosting.com, dns2.namecheaphosting.com
MXmx1-hosting.jellyfish.systems (5), mx2-hosting.jellyfish.systems (10), mx3-hosting.jellyfish.systems (20)
SPFpresent
DMARCabsent
CAA—
Wildcardoff
DNSSECnot signed
Resolver1.1.1.1:53

The SPF text record at bailbondshq.com is "v=spf1 +a +mx +ip4:162.0.232.145 +ip4:66.29.137.24 include:spf.web-hosting.com +ip4:184.94.213.170 ~all".

IPv4 address 184.94.213.170 answers for bailbondshq.com at resolver 1.1.1.1:53.

Mail exchanger mx1-hosting.jellyfish.systems has preference 5.

Mail exchanger mx2-hosting.jellyfish.systems has preference 10.

Mail exchanger mx3-hosting.jellyfish.systems has preference 20.

Hosting and geo

bailbondshq.com is placed in Los Angeles (West Los Angeles), United States by the local geolocation database (db-ip).

Address184.94.213.170
CountryUnited States
CityLos Angeles (West Los Angeles)
Sourcedb-ip

IP geolocation by DB-IP

SSL/TLS

The certificate for bailbondshq.com is not valid, with -192 days left and 2 subject alternative names. Source: tls:443.

IssuerSectigo RSA Domain Validation Secure Server CA
Subjectbailbondshq.com
Valid from21 April 2025
Valid until21 April 2026
Days left-192
SAN count2
ProtocolTLS 1.3
Sourcetls:443

Subject alternative names: bailbondshq.com, www.bailbondshq.com.

Validation result: certificate did not validate

Tech stack

Tech detection did not run.

Checkedno
Sourcewappalyzergo

On-page checks

The homepage fetch did not return a status code.

Statusnone

Get "https://bailbondshq.com/": tls: failed to verify certificate: x509: certificate has expired or is not yet valid: current time 2026-10-30T13:46:08Z is after 2026-04-21T23:59:59Z

Security

Family DNS for bailbondshq.com is clear, and URLhaus is clear. Source: family DNS and local lists.

Family DNSclear
URLhausclear
UT1—
Web Risknot run
Sourcefamily DNS and local lists
HSTSno
CSPno

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 0 of 20. A valid certificate, with extra points when it has at least 14 days left.

DNS hygiene 5 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.

Change history

  • October 2026: geo city changed from empty to Los Angeles (West Los Angeles).
  • October 2026: geo country changed from empty to United States.

Questions

Is bailbondshq.com safe?

The checks that ran did not produce a safety warning, and a score is not a promise that the site is safe.

Who hosts bailbondshq.com?

bailbondshq.com is placed in Los Angeles (West Los Angeles), United States.

When does bailbondshq.com expire?

bailbondshq.com expires on 1 July 2027 according to https://rdap.verisign.com/com/v1/domain/bailbondshq.com.

Who owns bailbondshq.com?

The registry did not return a person or a company for bailbondshq.com. RDAP often redacts the registrant. The registrar on file is NameCheap, Inc..

Sources

  • RDAP source https://rdap.verisign.com/com/v1/domain/bailbondshq.com at 2026-10-30T13:46:08Z
  • DNS source 1.1.1.1:53 at 2026-10-30T13:46:08Z
  • TLS source tls:443 at 2026-10-30T13:46:08Z
  • HTTP source https://bailbondshq.com/ at 2026-10-30T13:46:08Z
  • Tech source not available at 2026-10-30T13:46:08Z
  • Geo source db-ip at 2026-10-30T13:46:08Z
  • Safety source family DNS and local lists at 2026-10-30T13:46:08Z

Methodology

Related reports

No other indexable reports share this TLD, host, or registrar yet.

.com NameCheap, Inc.

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.

Removal policy

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.