brownhanky.com
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
60
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
60
brownhanky.com was registered on 18 Apr 2003 via NameCheap, Inc. and the registry expiry is 18 Apr 2027. WHOIS data came from RDAP at https://rdap.verisign.com/com/v1/domain/brownhanky.com.
brownhanky.com publishes 2 nameservers. DNSSEC is not signed.
brownhanky.com has 1 IPv4 address (89.185.234.130). The geolocation database places 89.185.234.130 in Brno střed, Czechia.
The TLS certificate from SSL.com TLS Issuing RSA CA R1 is valid and has 169 days left (TLS 1.3). The homepage answered HTTP 200.
Tech detection named Nginx, Ubuntu and reCAPTCHA. The fingerprints ran on the homepage that was already downloaded.
brownhanky.com was registered on 18 Apr 2003 via NameCheap, Inc.. The registry returned 1 status value and 4 nameservers from https://rdap.verisign.com/com/v1/domain/brownhanky.com.
| Registered | since 18 Apr 2003 |
|---|---|
| Created | 18 April 2003 |
| Updated | 31 August 2021 |
| Expires | 18 April 2027 |
| Registrar | NameCheap, Inc. |
| Status | client transfer prohibited |
| Nameservers | dns1.zoneedit.com, dns2.zoneedit.com, ns12.zoneedit.com, ns14.zoneedit.com |
| DNSSEC | no |
| Source | https://rdap.verisign.com/com/v1/domain/brownhanky.com |
brownhanky.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.zoneedit.com is published for brownhanky.com in the registration record from https://rdap.verisign.com/com/v1/domain/brownhanky.com.
Nameserver dns2.zoneedit.com is published for brownhanky.com in the registration record from https://rdap.verisign.com/com/v1/domain/brownhanky.com.
Nameserver ns12.zoneedit.com is published for brownhanky.com in the registration record from https://rdap.verisign.com/com/v1/domain/brownhanky.com.
Nameserver ns14.zoneedit.com is published for brownhanky.com in the registration record from https://rdap.verisign.com/com/v1/domain/brownhanky.com.
brownhanky.com has 1 address record, 1 mail exchanger and 2 nameservers, measured at 1.1.1.1:53.
| A | 89.185.234.130 |
|---|---|
| AAAA | — |
| NS | ns12.zoneedit.com, ns14.zoneedit.com |
| MX | mail.brownhanky.com (10) |
| SPF | present |
| DMARC | present |
| CAA | — |
| Wildcard | off |
| DNSSEC | not signed |
| Resolver | 1.1.1.1:53 |
The SPF text record at brownhanky.com is "v=spf1 include:spfdm-us-east-1.aliyun.com ip4:81.31.38.45 ip4:81.31.42.18 ip4:89.185.234.130 include:spf.mailjet.com include:amazonses.com -all".
The DMARC text record at _dmarc.brownhanky.com is "v=DMARC1; p=quarantine; fo=1; rua=mailto:[email protected];".
IPv4 address 89.185.234.130 answers for brownhanky.com at resolver 1.1.1.1:53.
Mail exchanger mail.brownhanky.com has preference 10.
brownhanky.com is placed in Brno střed, Czechia by the local geolocation database (db-ip).
| Address | 89.185.234.130 |
|---|---|
| Country | Czechia |
| City | Brno střed |
| Source | db-ip |
The certificate for brownhanky.com is valid, with 169 days left and 2 subject alternative names. Source: tls:443.
| Issuer | SSL.com TLS Issuing RSA CA R1 |
|---|---|
| Subject | *.brownhanky.com |
| Valid from | 2 October 2026 |
| Valid until | 18 April 2027 |
| Days left | 169 |
| SAN count | 2 |
| Protocol | TLS 1.3 |
| Source | tls:443 |
Subject alternative names: *.brownhanky.com, brownhanky.com.
Tech detection checked the fetched homepage and named 3 products. Source: wappalyzergo.
Nginx is filed under Web servers, Reverse proxies.
Ubuntu is filed under Operating systems.
reCAPTCHA is filed under Security.
The homepage returned HTTP 200 in 14 ms. The target title is 2 characters and the page has 0 H1 headings.
| Status | 200 |
|---|---|
| TTFB | 14 ms |
| Title length | 2 yes |
| Quoted title | "BH" |
| Meta description | "Bhsite" yes |
| H1 count | 0 |
| HSTS | no no |
| CSP | no |
| X-Frame-Options | — |
| Robots meta | — |
| Canonical | — |
| Language | — |
| Links | 0 |
| Images | 0 |
| Favicon | yes |
The quoted title and meta description are measurements of the other site. They are not this page's title or description.
Family DNS for brownhanky.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 brownhanky.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 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.
Cloudflare family DNS returned a block for brownhanky.com. That resolver covers adult and malware names.
brownhanky.com is placed in Brno střed, Czechia.
brownhanky.com expires on 18 April 2027 according to https://rdap.verisign.com/com/v1/domain/brownhanky.com.
The registry did not return a person or a company for brownhanky.com. RDAP often redacts the registrant. The registrar on file is NameCheap, Inc..
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.