fishbear.club
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
75
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
75
fishbear.club was registered on 27 Jun 2022 via GoDaddy.com, LLC and the registry expiry is 27 Jun 2027. WHOIS data came from RDAP at https://rdap.nic.club/domain/fishbear.club.
fishbear.club publishes 2 nameservers. DNSSEC is not signed.
fishbear.club has 1 IPv4 address (3.137.152.107). The geolocation database places 3.137.152.107 in Dublin, United States.
The TLS certificate from YE1 is valid and has 71 days left (TLS 1.3). The homepage answered HTTP 200.
Tech detection named Nginx and Ubuntu. The fingerprints ran on the homepage that was already downloaded.
No safety warning was recorded for fishbear.club in the checks that ran.
fishbear.club was registered on 27 Jun 2022 via GoDaddy.com, LLC. The registry returned 4 status values and 2 nameservers from https://rdap.nic.club/domain/fishbear.club.
| Registered | since 27 Jun 2022 |
|---|---|
| Created | 27 June 2022 |
| Updated | 21 March 2026 |
| Expires | 27 June 2027 |
| Registrar | GoDaddy.com, LLC |
| Status | client transfer prohibited, client renew prohibited, client update prohibited, client delete prohibited |
| Nameservers | ns03.domaincontrol.com, ns04.domaincontrol.com |
| DNSSEC | no |
| Source | https://rdap.nic.club/domain/fishbear.club |
fishbear.club 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.
fishbear.club 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.
fishbear.club 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.
fishbear.club 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.
Nameserver ns03.domaincontrol.com is published for fishbear.club in the registration record from https://rdap.nic.club/domain/fishbear.club.
Nameserver ns04.domaincontrol.com is published for fishbear.club in the registration record from https://rdap.nic.club/domain/fishbear.club.
fishbear.club has 1 address record, 1 mail exchanger and 2 nameservers, measured at 1.1.1.1:53.
| A | 3.137.152.107 |
|---|---|
| AAAA | — |
| NS | ns03.domaincontrol.com, ns04.domaincontrol.com |
| MX | smtp.google.com (1) Google |
| SPF | present |
| DMARC | present |
| CAA | — |
| Wildcard | off |
| DNSSEC | not signed |
| Resolver | 1.1.1.1:53 |
The SPF text record at fishbear.club is "v=spf1 include:mail.zendesk.com include:_spf.google.com-all".
The DMARC text record at _dmarc.fishbear.club is "v=DMARC1; p=none; rua=mailto:[email protected]".
IPv4 address 3.137.152.107 answers for fishbear.club at resolver 1.1.1.1:53.
Mail exchanger smtp.google.com has preference 1. The host is recognised as Google.
fishbear.club is placed in Dublin, United States by the local geolocation database (db-ip).
| Address | 3.137.152.107 |
|---|---|
| Country | United States |
| City | Dublin |
| Source | db-ip |
The certificate for fishbear.club is valid, with 71 days left and 2 subject alternative names. Source: tls:443.
| Issuer | YE1 |
|---|---|
| Subject | fishbear.club |
| Valid from | 13 October 2026 |
| Valid until | 11 January 2027 |
| Days left | 71 |
| SAN count | 2 |
| Protocol | TLS 1.3 |
| Source | tls:443 |
Subject alternative names: fishbear.club, www.fishbear.club.
Tech detection checked the fetched homepage and named 2 products. Source: wappalyzergo.
Nginx is filed under Web servers, Reverse proxies.
Ubuntu is filed under Operating systems.
The homepage returned HTTP 200 in 0 ms. The target title is 0 characters and the page has 0 H1 headings.
| Status | 200 |
|---|---|
| TTFB | 0 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 fishbear.club is clear, and URLhaus is clear. Source: family DNS and local lists.
| Family DNS | clear |
|---|---|
| URLhaus | clear |
| UT1 | — |
| Web Risk | not run |
| Source | family DNS and local lists |
| HSTS | no |
| CSP | no |
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 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.
The checks that ran did not produce a safety warning, and a score is not a promise that the site is safe.
fishbear.club is placed in Dublin, United States.
fishbear.club expires on 27 June 2027 according to https://rdap.nic.club/domain/fishbear.club.
The registry did not return a person or a company for fishbear.club. 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.