hbrowse.com
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
55
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
55
hbrowse.com was registered on 1 Jan 2010 via GoDaddy.com, LLC and the registry expiry is 1 Jan 2027. WHOIS data came from RDAP at https://rdap.verisign.com/com/v1/domain/hbrowse.com.
hbrowse.com publishes 2 nameservers. DNSSEC is not signed.
hbrowse.com has 2 IPv4 addresses (13.248.169.48, 76.223.54.146). The geolocation database places 13.248.169.48 in Montreal, Canada.
The TLS certificate from GoDaddy TLS Intermediate CA DV - R1v1 is valid and has 167 days left (TLS 1.3). The homepage answered HTTP 200.
hbrowse.com was registered on 1 Jan 2010 via GoDaddy.com, LLC. The registry returned 4 status values and 2 nameservers from https://rdap.verisign.com/com/v1/domain/hbrowse.com.
| Registered | since 1 Jan 2010 |
|---|---|
| Created | 1 January 2010 |
| Updated | 1 January 2026 |
| Expires | 1 January 2027 |
| Registrar | GoDaddy.com, LLC |
| Status | client delete prohibited, client renew prohibited, client transfer prohibited, client update prohibited |
| Nameservers | ns3.afternic.com, ns4.afternic.com |
| DNSSEC | no |
| Source | https://rdap.verisign.com/com/v1/domain/hbrowse.com |
hbrowse.com carries the status "client delete prohibited". The registrar has asked the registry to refuse a delete. This is an EPP status on the domain object. It does not say the website is safe, and it does not name the person who registered it.
hbrowse.com carries the status "client renew prohibited". The registrar has asked the registry to refuse a renewal. The expiry date still stands until a different status is set.
hbrowse.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.
hbrowse.com carries the status "client update prohibited". The registrar has asked the registry to refuse updates to the domain object. Contact and nameserver changes wait until the lock is lifted by the registrar of record.
Nameserver ns3.afternic.com is published for hbrowse.com in the registration record from https://rdap.verisign.com/com/v1/domain/hbrowse.com.
Nameserver ns4.afternic.com is published for hbrowse.com in the registration record from https://rdap.verisign.com/com/v1/domain/hbrowse.com.
hbrowse.com has 2 address records, 1 mail exchanger and 2 nameservers, measured at 1.1.1.1:53.
| A | 13.248.169.48, 76.223.54.146 |
|---|---|
| AAAA | — |
| NS | ns3.afternic.com, ns4.afternic.com |
| MX | (0) |
| SPF | present |
| DMARC | absent |
| CAA | — |
| Wildcard | on |
| DNSSEC | not signed |
| Resolver | 1.1.1.1:53 |
The SPF text record at hbrowse.com is "v=spf1 -all".
IPv4 address 13.248.169.48 answers for hbrowse.com at resolver 1.1.1.1:53.
IPv4 address 76.223.54.146 answers for hbrowse.com at resolver 1.1.1.1:53.
Mail exchanger has preference 0.
A random label under hbrowse.com also resolved, which means wildcard DNS is on.
hbrowse.com is placed in Montreal, Canada by the local geolocation database (db-ip).
| Address | 13.248.169.48 |
|---|---|
| Country | Canada |
| City | Montreal |
| Source | db-ip |
The certificate for hbrowse.com is valid, with 167 days left and 1 subject alternative name. Source: tls:443.
| Issuer | GoDaddy TLS Intermediate CA DV - R1v1 |
|---|---|
| Subject | hbrowse.com |
| Valid from | 30 September 2026 |
| Valid until | 16 April 2027 |
| Days left | 167 |
| SAN count | 1 |
| Protocol | TLS 1.3 |
| Source | tls:443 |
Subject alternative names: hbrowse.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 200 in 130 ms. The target title is 0 characters and the page has 0 H1 headings.
| Status | 200 |
|---|---|
| TTFB | 130 ms |
| Title length | 0 no |
| Quoted title | none |
| Meta description | none no |
| H1 count | 0 |
| 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 hbrowse.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 hbrowse.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.
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 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 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.
Cloudflare family DNS returned a block for hbrowse.com. That resolver covers adult and malware names.
hbrowse.com is placed in Montreal, Canada.
hbrowse.com expires on 1 January 2027 according to https://rdap.verisign.com/com/v1/domain/hbrowse.com.
The registry did not return a person or a company for hbrowse.com. RDAP often redacts the registrant. The registrar on file is GoDaddy.com, 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.