miningblocks.club
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
Online · 200SafeSSL: 80 days left5 years oldTranco #218434
70
miningblocks.club was registered on 30 Aug 2021 via GoDaddy.com, LLC and the registry expiry is 30 Aug 2028. WHOIS data came from RDAP at https://rdap.nic.club/domain/miningblocks.club.
miningblocks.club publishes 2 nameservers. DNSSEC is not signed.
miningblocks.club has 3 IPv4 addresses (104.26.10.87, 104.26.11.87, 172.67.74.204) and 3 IPv6 addresses (2606:4700:20::681a:a57, 2606:4700:20::681a:b57, 2606:4700:20::ac43:4acc). The geolocation database places 104.26.10.87 in Toronto, Canada.
The TLS certificate from WE1 is valid and has 80 days left (TLS 1.2). The homepage answered HTTP 200.
Tech detection named Bootstrap, Cloudflare, Cloudflare Browser Insights, HTTP/3, jQuery and jQuery CDN. The fingerprints ran on the homepage that was already downloaded.
No safety warning was recorded for miningblocks.club in the checks that ran.
Domain · RDAP/WHOIS
miningblocks.club was registered on 30 Aug 2021 via GoDaddy.com, LLC. The registry returned 4 status values and 2 nameservers from https://rdap.nic.club/domain/miningblocks.club.
| Registered | since 30 Aug 2021 |
|---|---|
| Created | 30 August 2021 |
| Updated | 5 September 2026 |
| Expires | 30 August 2028 |
| Registrar | GoDaddy.com, LLC |
| Status | client update prohibited, client transfer prohibited, client delete prohibited, client renew prohibited |
| Nameservers | val.ns.cloudflare.com, josh.ns.cloudflare.com |
| DNSSEC | no |
| Source | https://rdap.nic.club/domain/miningblocks.club |
miningblocks.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.
miningblocks.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.
miningblocks.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.
miningblocks.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.
Nameserver val.ns.cloudflare.com is published for miningblocks.club in the registration record from https://rdap.nic.club/domain/miningblocks.club.
Nameserver josh.ns.cloudflare.com is published for miningblocks.club in the registration record from https://rdap.nic.club/domain/miningblocks.club.
DNS
miningblocks.club has 6 address records, 1 mail exchanger and 2 nameservers, measured at 1.1.1.1:53.
| A | 104.26.10.87, 104.26.11.87, 172.67.74.204 |
|---|---|
| AAAA | 2606:4700:20::681a:a57, 2606:4700:20::681a:b57, 2606:4700:20::ac43:4acc |
| NS | josh.ns.cloudflare.com, val.ns.cloudflare.com |
| MX | igw05.site4now.net (10) |
| SPF | present |
| DMARC | absent |
| CAA | — |
| Wildcard | on |
| DNSSEC | not signed |
| Resolver | 1.1.1.1:53 |
The SPF text record at miningblocks.club is "v=spf1 a mx include:_spf.site4now.net ?all".
IPv4 address 104.26.10.87 answers for miningblocks.club at resolver 1.1.1.1:53.
IPv4 address 104.26.11.87 answers for miningblocks.club at resolver 1.1.1.1:53.
IPv4 address 172.67.74.204 answers for miningblocks.club at resolver 1.1.1.1:53.
IPv6 address 2606:4700:20::681a:a57 answers for miningblocks.club at resolver 1.1.1.1:53.
IPv6 address 2606:4700:20::681a:b57 answers for miningblocks.club at resolver 1.1.1.1:53.
IPv6 address 2606:4700:20::ac43:4acc answers for miningblocks.club at resolver 1.1.1.1:53.
Mail exchanger igw05.site4now.net has preference 10.
A random label under miningblocks.club also resolved, which means wildcard DNS is on.
Hosting and geo
miningblocks.club is placed in Toronto, Canada by the local geolocation database (db-ip).
| Address | 104.26.10.87 |
|---|---|
| Country | Canada |
| City | Toronto |
| Source | db-ip |
SSL/TLS
The certificate for miningblocks.club is valid, with 80 days left and 2 subject alternative names. Source: tls:443.
| Issuer | WE1 |
|---|---|
| Subject | miningblocks.club |
| Valid from | 21 October 2026 |
| Valid until | 19 January 2027 |
| Days left | 80 |
| SAN count | 2 |
| Protocol | TLS 1.2 |
| Source | tls:443 |
Subject alternative names: *.miningblocks.club, miningblocks.club.
Tech stack
Tech detection checked the fetched homepage and named 6 products. Source: wappalyzergo.
- Bootstrap · UI frameworks
- Cloudflare · CDN
- Cloudflare Browser Insights · Analytics, RUM
- HTTP/3 · Miscellaneous
- jQuery · JavaScript libraries
- jQuery CDN · CDN
Bootstrap is filed under UI frameworks.
Cloudflare is filed under CDN.
Cloudflare Browser Insights is filed under Analytics, RUM.
HTTP/3 is filed under Miscellaneous.
jQuery is filed under JavaScript libraries.
jQuery CDN is filed under CDN.
On-page checks
The homepage returned HTTP 200 in 520 ms. The target title is 13 characters and the page has 0 H1 headings.
| Status | 200 |
|---|---|
| TTFB | 520 ms |
| Title length | 13 yes |
| Quoted title | "Mining blocks" |
| Meta description | none no |
| H1 count | 0 |
| HSTS | no no |
| CSP | no |
| X-Frame-Options | — |
| Robots meta | — |
| Canonical | — |
| Language | en |
| Links | 7 |
| Images | 9 |
| Favicon | yes |
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 miningblocks.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.
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 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
First checked on 30 October 2026; changes will appear here.
Questions
Is miningblocks.club 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 miningblocks.club?
miningblocks.club is placed in Toronto, Canada.
When does miningblocks.club expire?
miningblocks.club expires on 30 August 2028 according to https://rdap.nic.club/domain/miningblocks.club.
Who owns miningblocks.club?
The registry did not return a person or a company for miningblocks.club. RDAP often redacts the registrant. The registrar on file is GoDaddy.com, LLC.
Sources
- RDAP source https://rdap.nic.club/domain/miningblocks.club at 2026-10-30T13:37:11Z
- DNS source 1.1.1.1:53 at 2026-10-30T13:37:11Z
- TLS source tls:443 at 2026-10-30T13:37:11Z
- HTTP source https://miningblocks.club/ at 2026-10-30T13:37:11Z
- Tech source wappalyzergo at 2026-10-30T13:37:11Z
- Geo source db-ip at 2026-10-30T13:37:11Z
- Safety source family DNS and local lists at 2026-10-30T13:37:11Z
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.