bearbit.co

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

Online · 200SafeSSL: 88 days left2 years old

One re-check per domain each UTC day.

75

bearbit.co was registered on 20 Feb 2024 via GoDaddy.com, LLC and the registry expiry is 20 Feb 2027. WHOIS data came from RDAP at https://rdap.registry.co/co/domain/bearbit.co.

bearbit.co publishes 2 nameservers. DNSSEC is not signed.

bearbit.co has 1 IPv4 address (138.199.46.68) and 1 IPv6 address (2400:52e0:1500::1274:1). The geolocation database places 138.199.46.68 in Singapore, Singapore.

The TLS certificate from YR1 is valid and has 88 days left (TLS 1.3). The homepage answered HTTP 200.

Tech detection named Cloudflare, HTTP/3 and PHP. The fingerprints ran on the homepage that was already downloaded.

No safety warning was recorded for bearbit.co in the checks that ran.

Domain · RDAP/WHOIS

bearbit.co was registered on 20 Feb 2024 via GoDaddy.com, LLC. The registry returned 4 status values and 2 nameservers from https://rdap.registry.co/co/domain/bearbit.co.

Registeredsince 20 Feb 2024
Created20 February 2024
Updated7 May 2026
Expires20 February 2027
RegistrarGoDaddy.com, LLC
Statusclient renew prohibited, client transfer prohibited, client update prohibited, client delete prohibited
Nameserverskiki.bunny.net, coco.bunny.net
DNSSECno
Sourcehttps://rdap.registry.co/co/domain/bearbit.co

bearbit.co 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.

bearbit.co 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.

bearbit.co 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.

bearbit.co 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 kiki.bunny.net is published for bearbit.co in the registration record from https://rdap.registry.co/co/domain/bearbit.co.

Nameserver coco.bunny.net is published for bearbit.co in the registration record from https://rdap.registry.co/co/domain/bearbit.co.

DNS

bearbit.co has 2 address records, 0 mail exchangers and 2 nameservers, measured at 1.1.1.1:53.

A138.199.46.68
AAAA2400:52e0:1500::1274:1
NScoco.bunny.net, kiki.bunny.net
MX—
SPFabsent
DMARCabsent
CAA—
Wildcardoff
DNSSECnot signed
Resolver1.1.1.1:53

IPv4 address 138.199.46.68 answers for bearbit.co at resolver 1.1.1.1:53.

IPv6 address 2400:52e0:1500::1274:1 answers for bearbit.co at resolver 1.1.1.1:53.

Hosting and geo

bearbit.co is placed in Singapore, Singapore by the local geolocation database (db-ip).

Address138.199.46.68
CountrySingapore
CitySingapore
Sourcedb-ip

IP geolocation by DB-IP

SSL/TLS

The certificate for bearbit.co is valid, with 88 days left and 1 subject alternative name. Source: tls:443.

IssuerYR1
Subjectbearbit.co
Valid from29 October 2026
Valid until27 January 2027
Days left88
SAN count1
ProtocolTLS 1.3
Sourcetls:443

Subject alternative names: bearbit.co.

Tech stack

Tech detection checked the fetched homepage and named 3 products. Source: wappalyzergo.

  • Cloudflare · CDN
  • HTTP/3 · Miscellaneous
  • PHP · Programming languages

Cloudflare is filed under CDN.

HTTP/3 is filed under Miscellaneous.

PHP is filed under Programming languages.

On-page checks

The homepage returned HTTP 200 in 0 ms. The target title is 0 characters and the page has 0 H1 headings.

Status200
TTFB0 ms
Title length0 no
Quoted titlenone
Meta descriptionnone no
H1 count0
HSTSno no
CSPyes
X-Frame-OptionsSAMEORIGIN
Robots meta—
Canonical—
Language—
Links0
Images0
Faviconno

The quoted title and meta description are measurements of the other site. They are not this page's title or description.

Security

Family DNS for bearbit.co 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
CSPyes

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 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 0 of 20. SPF, DMARC, CAA, and DNSSEC are five points each.

Security headers 10 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: rdap created changed from empty to 2024-02-20T14:05:54.0Z.
  • October 2026: rdap dnssec changed from unknown to no.
  • October 2026: rdap expires changed from empty to 2027-02-20T23:59:59.0Z.
  • October 2026: rdap nameservers changed from empty to coco.bunny.net,kiki.bunny.net.
  • October 2026: rdap registered changed from unknown to yes.
  • October 2026: rdap registrar changed from empty to GoDaddy.com, LLC.
  • October 2026: rdap statuses changed from empty to client delete prohibited,client renew prohibited,client transfer prohibited,client update prohibited.
  • October 2026: rdap updated changed from empty to 2026-05-07T10:13:20.0Z.
  • October 2026: dns a changed from 138.199.46.65 to 138.199.46.68.
  • October 2026: dns aaaa changed from 2400:52e0:1500::868:1 to 2400:52e0:1500::1274:1.
  • October 2026: geo city changed from empty to Singapore.
  • October 2026: geo country changed from empty to Singapore.

Questions

Is bearbit.co 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 bearbit.co?

bearbit.co is placed in Singapore, Singapore.

When does bearbit.co expire?

bearbit.co expires on 20 February 2027 according to https://rdap.registry.co/co/domain/bearbit.co.

Who owns bearbit.co?

The registry did not return a person or a company for bearbit.co. RDAP often redacts the registrant. The registrar on file is GoDaddy.com, LLC.

Sources

  • RDAP source https://rdap.registry.co/co/domain/bearbit.co at 2026-10-30T13:38:21Z
  • DNS source 1.1.1.1:53 at 2026-10-30T13:38:21Z
  • TLS source tls:443 at 2026-10-30T13:38:21Z
  • HTTP source https://bearbit.co/ at 2026-10-30T13:38:21Z
  • Tech source wappalyzergo at 2026-10-30T13:38:21Z
  • Geo source db-ip at 2026-10-30T13:38:21Z
  • Safety source family DNS and local lists at 2026-10-30T13:38:21Z

Methodology

Related reports

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

.co GoDaddy.com, LLC

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.