btdig.com
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
OfflineFamily DNS blocked19 years oldTranco #37901
20
btdig.com was registered on 24 Mar 2007 via Tucows Domains Inc. and the registry expiry is 24 Mar 2028. WHOIS data came from RDAP at https://rdap.verisign.com/com/v1/domain/btdig.com.
btdig.com publishes 3 nameservers. DNSSEC is not signed.
btdig.com has 1 IPv4 address (45.8.125.206) and 1 IPv6 address (2001:470:6192:6a1:3528:2d4a:e534:8724). The geolocation database places 45.8.125.206 in Moscow, Russia.
Domain · RDAP/WHOIS
btdig.com was registered on 24 Mar 2007 via Tucows Domains Inc.. The registry returned 2 status values and 3 nameservers from https://rdap.verisign.com/com/v1/domain/btdig.com.
| Registered | since 24 Mar 2007 |
|---|---|
| Created | 24 March 2007 |
| Updated | 16 September 2026 |
| Expires | 24 March 2028 |
| Registrar | Tucows Domains Inc. |
| Status | client transfer prohibited, client update prohibited |
| Nameservers | ns1.btdig.com, ns2.btdig.com, ns3.btdig.com |
| DNSSEC | no |
| Source | https://rdap.verisign.com/com/v1/domain/btdig.com |
btdig.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.
btdig.com 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.
Nameserver ns1.btdig.com is published for btdig.com in the registration record from https://rdap.verisign.com/com/v1/domain/btdig.com.
Nameserver ns2.btdig.com is published for btdig.com in the registration record from https://rdap.verisign.com/com/v1/domain/btdig.com.
Nameserver ns3.btdig.com is published for btdig.com in the registration record from https://rdap.verisign.com/com/v1/domain/btdig.com.
DNS
btdig.com has 2 address records, 1 mail exchanger and 3 nameservers, measured at 1.1.1.1:53.
| A | 45.8.125.206 |
|---|---|
| AAAA | 2001:470:6192:6a1:3528:2d4a:e534:8724 |
| NS | ns1.btdig.com, ns2.btdig.com, ns3.btdig.com |
| MX | mail.tutanota.de (10) |
| SPF | absent |
| DMARC | present |
| CAA | — |
| Wildcard | on |
| DNSSEC | not signed |
| Resolver | 1.1.1.1:53 |
The DMARC text record at _dmarc.btdig.com is "v=DMARC1; p=quarantine; adkim=s".
IPv4 address 45.8.125.206 answers for btdig.com at resolver 1.1.1.1:53.
IPv6 address 2001:470:6192:6a1:3528:2d4a:e534:8724 answers for btdig.com at resolver 1.1.1.1:53.
Mail exchanger mail.tutanota.de has preference 10.
A random label under btdig.com also resolved, which means wildcard DNS is on.
Hosting and geo
btdig.com is placed in Moscow, Russia by the local geolocation database (db-ip).
| Address | 45.8.125.206 |
|---|---|
| Country | Russia |
| City | Moscow |
| Source | db-ip |
SSL/TLS
No TLS certificate was read for btdig.com on port 443.
| Available | no |
|---|---|
| Source | tls:443 |
dial tcp 45.8.125.206:443: 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 btdig.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 btdig.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.
Score breakdown
Availability 10 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 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.
Change history
- October 2026: dns aaaa changed from 2001:470:6192:6b8f:8015:e364:ad9e:c7fd to 2001:470:6192:6a1:3528:2d4a:e534:8724.
- October 2026: geo city changed from empty to Moscow.
- October 2026: geo country changed from empty to Russia.
Questions
Is btdig.com safe?
Cloudflare family DNS returned a block for btdig.com. That resolver covers adult and malware names.
Who hosts btdig.com?
btdig.com is placed in Moscow, Russia.
When does btdig.com expire?
btdig.com expires on 24 March 2028 according to https://rdap.verisign.com/com/v1/domain/btdig.com.
Who owns btdig.com?
The registry did not return a person or a company for btdig.com. RDAP often redacts the registrant. The registrar on file is Tucows Domains Inc..
Sources
- RDAP source https://rdap.verisign.com/com/v1/domain/btdig.com at 2026-10-30T13:48:07Z
- DNS source 1.1.1.1:53 at 2026-10-30T13:48:07Z
- TLS source tls:443 at 2026-10-30T13:48:07Z
- HTTP source https://btdig.com/ at 2026-10-30T13:48:07Z
- Tech source not available at 2026-10-30T13:48:07Z
- Geo source db-ip at 2026-10-30T13:48:07Z
- Safety source family DNS and local lists at 2026-10-30T13:48:07Z
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.