mh160.cc
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
HTTP 403SafeSSL: 45 days left8 years old
60
mh160.cc was registered on 31 Aug 2018 via Alibaba Cloud Computing (Beijing) Co., Ltd. and the registry expiry is 31 Aug 2027. WHOIS data came from RDAP at https://tld-rdap.verisign.com/cc/v1/domain/mh160.cc.
mh160.cc publishes 2 nameservers. DNSSEC is not signed.
mh160.cc has 3 IPv4 addresses (104.26.0.64, 104.26.1.64, 172.67.71.205) and 3 IPv6 addresses (2606:4700:20::681a:140, 2606:4700:20::681a:40, 2606:4700:20::ac43:47cd). The geolocation database places 104.26.0.64 in Toronto, Canada.
The TLS certificate from WE1 is valid and has 45 days left (TLS 1.3).
Tech detection named Cloudflare. The fingerprints ran on the homepage that was already downloaded.
No safety warning was recorded for mh160.cc in the checks that ran.
Domain · RDAP/WHOIS
mh160.cc was registered on 31 Aug 2018 via Alibaba Cloud Computing (Beijing) Co., Ltd.. The registry returned 1 status value and 2 nameservers from https://tld-rdap.verisign.com/cc/v1/domain/mh160.cc.
| Registered | since 31 Aug 2018 |
|---|---|
| Created | 31 August 2018 |
| Updated | 11 October 2025 |
| Expires | 31 August 2027 |
| Registrar | Alibaba Cloud Computing (Beijing) Co., Ltd. |
| Status | active |
| Nameservers | dns19.hichina.com, dns20.hichina.com |
| DNSSEC | no |
| Source | https://tld-rdap.verisign.com/cc/v1/domain/mh160.cc |
Nameserver dns19.hichina.com is published for mh160.cc in the registration record from https://tld-rdap.verisign.com/cc/v1/domain/mh160.cc.
Nameserver dns20.hichina.com is published for mh160.cc in the registration record from https://tld-rdap.verisign.com/cc/v1/domain/mh160.cc.
DNS
mh160.cc has 6 address records, 0 mail exchangers and 2 nameservers, measured at 1.1.1.1:53.
| A | 104.26.0.64, 104.26.1.64, 172.67.71.205 |
|---|---|
| AAAA | 2606:4700:20::681a:140, 2606:4700:20::681a:40, 2606:4700:20::ac43:47cd |
| NS | dns19.hichina.com, dns20.hichina.com |
| MX | — |
| SPF | absent |
| DMARC | absent |
| CAA | — |
| Wildcard | off |
| DNSSEC | not signed |
| Resolver | 1.1.1.1:53 |
IPv4 address 104.26.0.64 answers for mh160.cc at resolver 1.1.1.1:53.
IPv4 address 104.26.1.64 answers for mh160.cc at resolver 1.1.1.1:53.
IPv4 address 172.67.71.205 answers for mh160.cc at resolver 1.1.1.1:53.
IPv6 address 2606:4700:20::681a:140 answers for mh160.cc at resolver 1.1.1.1:53.
IPv6 address 2606:4700:20::681a:40 answers for mh160.cc at resolver 1.1.1.1:53.
IPv6 address 2606:4700:20::ac43:47cd answers for mh160.cc at resolver 1.1.1.1:53.
Hosting and geo
mh160.cc is placed in Toronto, Canada by the local geolocation database (db-ip).
| Address | 104.26.0.64 |
|---|---|
| Country | Canada |
| City | Toronto |
| Source | db-ip |
SSL/TLS
The certificate for mh160.cc is valid, with 45 days left and 1 subject alternative name. Source: tls:443.
| Issuer | WE1 |
|---|---|
| Subject | mh160.cc |
| Valid from | 17 September 2026 |
| Valid until | 16 December 2026 |
| Days left | 45 |
| SAN count | 1 |
| Protocol | TLS 1.3 |
| Source | tls:443 |
Subject alternative names: mh160.cc.
Tech stack
Tech detection checked the fetched homepage and named 1 product. Source: wappalyzergo.
- Cloudflare · CDN
Cloudflare is filed under CDN.
On-page checks
The homepage returned HTTP 403 in 34 ms. The target title is 16 characters and the page has 0 H1 headings.
| Status | 403 |
|---|---|
| TTFB | 34 ms |
| Title length | 16 yes |
| Quoted title | "Just a moment..." |
| Meta description | none no |
| H1 count | 0 |
| HSTS | no no |
| CSP | yes |
| X-Frame-Options | SAMEORIGIN |
| Robots meta | noindex,nofollow |
| Canonical | — |
| Language | en-US |
| Links | 0 |
| Images | 0 |
| Favicon | no |
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 mh160.cc 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 | yes |
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 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
First checked on 30 October 2026; changes will appear here.
Questions
Is mh160.cc 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 mh160.cc?
mh160.cc is placed in Toronto, Canada.
When does mh160.cc expire?
mh160.cc expires on 31 August 2027 according to https://tld-rdap.verisign.com/cc/v1/domain/mh160.cc.
Who owns mh160.cc?
The registry did not return a person or a company for mh160.cc. RDAP often redacts the registrant. The registrar on file is Alibaba Cloud Computing (Beijing) Co., Ltd..
Sources
- RDAP source https://tld-rdap.verisign.com/cc/v1/domain/mh160.cc at 2026-10-30T13:34:30Z
- DNS source 1.1.1.1:53 at 2026-10-30T13:34:30Z
- TLS source tls:443 at 2026-10-30T13:34:30Z
- HTTP source https://mh160.cc/ at 2026-10-30T13:34:30Z
- Tech source wappalyzergo at 2026-10-30T13:34:30Z
- Geo source db-ip at 2026-10-30T13:34:30Z
- Safety source family DNS and local lists at 2026-10-30T13:34:30Z
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.