botrecord.live
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
OfflineSafeSSL: 74 days leftUnder 1 year old
47
botrecord.live was registered on 3 Mar 2026 via CommuniGal Communication Ltd. and the registry expiry is 3 Mar 2027. WHOIS data came from RDAP at https://rdap.identitydigital.services/rdap/domain/botrecord.live.
botrecord.live publishes 2 nameservers. DNSSEC is not signed.
botrecord.live has 1 IPv4 address (212.92.105.21). The geolocation database places 212.92.105.21 in Roosendaal, The Netherlands.
The TLS certificate from YR1 is valid and has 74 days left (TLS 1.3).
No safety warning was recorded for botrecord.live in the checks that ran.
Domain · RDAP/WHOIS
botrecord.live was registered on 3 Mar 2026 via CommuniGal Communication Ltd.. The registry returned 1 status value and 2 nameservers from https://rdap.identitydigital.services/rdap/domain/botrecord.live.
| Registered | since 3 Mar 2026 |
|---|---|
| Created | 3 March 2026 |
| Updated | 14 October 2026 |
| Expires | 3 March 2027 |
| Registrar | CommuniGal Communication Ltd. |
| Status | client transfer prohibited |
| Nameservers | ns1.hostresolver.com, ns2.hostresolver.com |
| DNSSEC | no |
| Source | https://rdap.identitydigital.services/rdap/domain/botrecord.live |
botrecord.live 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 ns1.hostresolver.com is published for botrecord.live in the registration record from https://rdap.identitydigital.services/rdap/domain/botrecord.live.
Nameserver ns2.hostresolver.com is published for botrecord.live in the registration record from https://rdap.identitydigital.services/rdap/domain/botrecord.live.
DNS
botrecord.live has 1 address record, 0 mail exchangers and 2 nameservers, measured at 1.1.1.1:53.
| A | 212.92.105.21 |
|---|---|
| AAAA | — |
| NS | ns1.hostresolver.com, ns2.hostresolver.com |
| MX | — |
| SPF | absent |
| DMARC | absent |
| CAA | — |
| Wildcard | on |
| DNSSEC | not signed |
| Resolver | 1.1.1.1:53 |
IPv4 address 212.92.105.21 answers for botrecord.live at resolver 1.1.1.1:53.
A random label under botrecord.live also resolved, which means wildcard DNS is on.
Hosting and geo
botrecord.live is placed in Roosendaal, The Netherlands by the local geolocation database (db-ip).
| Address | 212.92.105.21 |
|---|---|
| Country | The Netherlands |
| City | Roosendaal |
| Source | db-ip |
SSL/TLS
The certificate for botrecord.live is valid, with 74 days left and 2 subject alternative names. Source: tls:443.
| Issuer | YR1 |
|---|---|
| Subject | botrecord.live |
| Valid from | 15 October 2026 |
| Valid until | 13 January 2027 |
| Days left | 74 |
| SAN count | 2 |
| Protocol | TLS 1.3 |
| Source | tls:443 |
Subject alternative names: *.botrecord.live, botrecord.live.
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 |
|---|
Head "http://surveymrs.com": read tcp 10.0.0.3:53726->208.91.196.145:80: read: connection reset by peer
Security
Family DNS for botrecord.live 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 10 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 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 2 of 5. Five points at one year, two points at 30 days.
Change history
- October 2026: dns a changed from 212.92.105.23 to 212.92.105.21.
- October 2026: geo city changed from empty to Roosendaal.
- October 2026: geo country changed from empty to The Netherlands.
Questions
Is botrecord.live 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 botrecord.live?
botrecord.live is placed in Roosendaal, The Netherlands.
When does botrecord.live expire?
botrecord.live expires on 3 March 2027 according to https://rdap.identitydigital.services/rdap/domain/botrecord.live.
Who owns botrecord.live?
The registry did not return a person or a company for botrecord.live. RDAP often redacts the registrant. The registrar on file is CommuniGal Communication Ltd..
Sources
- RDAP source https://rdap.identitydigital.services/rdap/domain/botrecord.live at 2026-10-30T14:41:58Z
- DNS source 1.1.1.1:53 at 2026-10-30T14:41:58Z
- TLS source tls:443 at 2026-10-30T14:41:58Z
- HTTP source https://botrecord.live/ at 2026-10-30T14:41:58Z
- Tech source not available at 2026-10-30T14:41:58Z
- Geo source db-ip at 2026-10-30T14:41:58Z
- Safety source family DNS and local lists at 2026-10-30T14:41:58Z
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.