bd2020.co
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
OfflineSafe5 years old
25
bd2020.co was registered on 4 Mar 2021 via GoDaddy.com, LLC and the registry expiry is 4 Mar 2027. WHOIS data came from RDAP at https://rdap.registry.co/co/domain/bd2020.co.
No safety warning was recorded for bd2020.co in the checks that ran.
Domain · RDAP/WHOIS
bd2020.co was registered on 4 Mar 2021 via GoDaddy.com, LLC. The registry returned 4 status values and 2 nameservers from https://rdap.registry.co/co/domain/bd2020.co.
| Registered | since 4 Mar 2021 |
|---|---|
| Created | 4 March 2021 |
| Updated | 7 May 2026 |
| Expires | 4 March 2027 |
| Registrar | GoDaddy.com, LLC |
| Status | client renew prohibited, client transfer prohibited, client update prohibited, client delete prohibited |
| Nameservers | ns4.dnsv2.com, ns3.dnsv2.com |
| DNSSEC | yes |
| Source | https://rdap.registry.co/co/domain/bd2020.co |
bd2020.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.
bd2020.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.
bd2020.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.
bd2020.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 ns4.dnsv2.com is published for bd2020.co in the registration record from https://rdap.registry.co/co/domain/bd2020.co.
Nameserver ns3.dnsv2.com is published for bd2020.co in the registration record from https://rdap.registry.co/co/domain/bd2020.co.
DNS
bd2020.co has 0 address records, 0 mail exchangers and 0 nameservers, measured at 1.1.1.1:53.
| A | — |
|---|---|
| AAAA | — |
| NS | — |
| MX | — |
| SPF | absent |
| DMARC | absent |
| CAA | — |
| Wildcard | off |
| DNSSEC | signed |
| Resolver | 1.1.1.1:53 |
read udp 10.0.0.3:44963->8.8.8.8:53: i/o timeout
Hosting and geo
Geolocation for bd2020.co is not available. No local city or ASN database is installed, so this report does not guess a country.
| Geolocation | not available |
|---|---|
| Source | maxmind |
SSL/TLS
No TLS certificate was read for bd2020.co on port 443.
| Available | no |
|---|---|
| Source | tls:443 |
dial tcp: lookup bd2020.co: i/o timeout
Tech stack
Tech detection did not run.
| Checked | no |
|---|---|
| Source | wappalyzergo |
On-page checks
The homepage fetch did not return a status code.
| Status | none |
|---|
context deadline exceeded
Security
Family DNS for bd2020.co 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.
Score breakdown
Availability 0 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: rdap created changed from empty to 2021-03-04T08:24:02.0Z.
- October 2026: rdap dnssec changed from unknown to yes.
- October 2026: rdap expires changed from empty to 2027-03-04T23:59:59.0Z.
- October 2026: rdap nameservers changed from empty to ns3.dnsv2.com,ns4.dnsv2.com.
- 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:15:21.0Z.
Questions
Is bd2020.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 bd2020.co?
The host network is not available without a local geolocation database.
When does bd2020.co expire?
bd2020.co expires on 4 March 2027 according to https://rdap.registry.co/co/domain/bd2020.co.
Who owns bd2020.co?
The registry did not return a person or a company for bd2020.co. RDAP often redacts the registrant. The registrar on file is GoDaddy.com, LLC.
Sources
- RDAP source https://rdap.registry.co/co/domain/bd2020.co at 2026-10-30T13:38:31Z
- DNS source 1.1.1.1:53 at 2026-10-30T13:38:31Z
- TLS source tls:443 at 2026-10-30T13:38:31Z
- HTTP source https://bd2020.co/ at 2026-10-30T13:38:31Z
- Tech source not available at 2026-10-30T13:38:31Z
- Geo source db-ip at 2026-10-30T13:38:31Z
- Safety source family DNS and local lists at 2026-10-30T13:38:31Z
Related reports
No other indexable reports share this TLD, host, or registrar yet.
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.
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.