hiperdex.com
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
Online · 200Family DNS blockedSSL: 77 days left7 years oldTranco #161054
70
hiperdex.com was registered on 30 Jul 2019 via Tucows Domains Inc. and the registry expiry is 30 Jul 2027. WHOIS data came from RDAP at https://rdap.verisign.com/com/v1/domain/hiperdex.com.
hiperdex.com publishes 2 nameservers. DNSSEC is not signed.
hiperdex.com has 3 IPv4 addresses (104.26.0.160, 104.26.1.160, 172.67.68.20) and 3 IPv6 addresses (2606:4700:20::681a:1a0, 2606:4700:20::681a:a0, 2606:4700:20::ac43:4414). The geolocation database places 104.26.0.160 in Toronto, Canada.
The TLS certificate from WE1 is valid and has 77 days left (TLS 1.3). The homepage answered HTTP 200.
Tech detection named Cloudflare, Cloudflare Browser Insights, Google Analytics, HSTS and HTTP/3. The fingerprints ran on the homepage that was already downloaded.
Domain · RDAP/WHOIS
hiperdex.com was registered on 30 Jul 2019 via Tucows Domains Inc.. The registry returned 2 status values and 2 nameservers from https://rdap.verisign.com/com/v1/domain/hiperdex.com.
| Registered | since 30 Jul 2019 |
|---|---|
| Created | 30 July 2019 |
| Updated | 4 July 2025 |
| Expires | 30 July 2027 |
| Registrar | Tucows Domains Inc. |
| Status | client transfer prohibited, client update prohibited |
| Nameservers | emma.ns.cloudflare.com, lee.ns.cloudflare.com |
| DNSSEC | no |
| Source | https://rdap.verisign.com/com/v1/domain/hiperdex.com |
hiperdex.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.
hiperdex.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 emma.ns.cloudflare.com is published for hiperdex.com in the registration record from https://rdap.verisign.com/com/v1/domain/hiperdex.com.
Nameserver lee.ns.cloudflare.com is published for hiperdex.com in the registration record from https://rdap.verisign.com/com/v1/domain/hiperdex.com.
DNS
hiperdex.com has 6 address records, 1 mail exchanger and 2 nameservers, measured at 1.1.1.1:53.
| A | 104.26.0.160, 104.26.1.160, 172.67.68.20 |
|---|---|
| AAAA | 2606:4700:20::681a:1a0, 2606:4700:20::681a:a0, 2606:4700:20::ac43:4414 |
| NS | emma.ns.cloudflare.com, lee.ns.cloudflare.com |
| MX | mail.rawdex.net (10) |
| SPF | present |
| DMARC | present |
| CAA | — |
| Wildcard | off |
| DNSSEC | not signed |
| Resolver | 1.1.1.1:53 |
The SPF text record at hiperdex.com is "v=spf1 mx ip4:23.26.125.123 ~all".
The DMARC text record at _dmarc.hiperdex.com is "v=DMARC1; p=none;".
IPv4 address 104.26.0.160 answers for hiperdex.com at resolver 1.1.1.1:53.
IPv4 address 104.26.1.160 answers for hiperdex.com at resolver 1.1.1.1:53.
IPv4 address 172.67.68.20 answers for hiperdex.com at resolver 1.1.1.1:53.
IPv6 address 2606:4700:20::681a:1a0 answers for hiperdex.com at resolver 1.1.1.1:53.
IPv6 address 2606:4700:20::681a:a0 answers for hiperdex.com at resolver 1.1.1.1:53.
IPv6 address 2606:4700:20::ac43:4414 answers for hiperdex.com at resolver 1.1.1.1:53.
Mail exchanger mail.rawdex.net has preference 10.
Hosting and geo
hiperdex.com is placed in Toronto, Canada by the local geolocation database (db-ip).
| Address | 104.26.0.160 |
|---|---|
| Country | Canada |
| City | Toronto |
| Source | db-ip |
SSL/TLS
The certificate for hiperdex.com is valid, with 77 days left and 2 subject alternative names. Source: tls:443.
| Issuer | WE1 |
|---|---|
| Subject | hiperdex.com |
| Valid from | 19 October 2026 |
| Valid until | 17 January 2027 |
| Days left | 77 |
| SAN count | 2 |
| Protocol | TLS 1.3 |
| Source | tls:443 |
Subject alternative names: *.hiperdex.com, hiperdex.com.
Tech stack
Tech detection checked the fetched homepage and named 5 products. Source: wappalyzergo.
- Cloudflare · CDN
- Cloudflare Browser Insights · Analytics, RUM
- Google Analytics · Analytics
- HSTS · Security
- HTTP/3 · Miscellaneous
Cloudflare is filed under CDN.
Cloudflare Browser Insights is filed under Analytics, RUM.
Google Analytics is filed under Analytics.
HSTS is filed under Security.
HTTP/3 is filed under Miscellaneous.
On-page checks
The homepage returned HTTP 200 in 122 ms. The target title is 49 characters and the page has 0 H1 headings.
| Status | 200 |
|---|---|
| TTFB | 122 ms |
| Title length | 49 yes |
| Quoted title | "Read Manhwa, Manga and Webtoons Online | HIPERDEX" |
| Meta description | "Read manga, manhwa and webtoons online in English on HiperDEX. Discover action, romance, fantasy, isekai and adult series updated daily." yes |
| H1 count | 0 |
| HSTS | yes yes |
| CSP | no |
| X-Frame-Options | DENY |
| Robots meta | — |
| Canonical | https://hiperdex.com |
| Language | en |
| Links | 0 |
| Images | 0 |
| 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 hiperdex.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 | yes |
| CSP | no |
Cloudflare family DNS returned a block for hiperdex.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 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 10 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 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
First checked on 30 October 2026; changes will appear here.
Questions
Is hiperdex.com safe?
Cloudflare family DNS returned a block for hiperdex.com. That resolver covers adult and malware names.
Who hosts hiperdex.com?
hiperdex.com is placed in Toronto, Canada.
When does hiperdex.com expire?
hiperdex.com expires on 30 July 2027 according to https://rdap.verisign.com/com/v1/domain/hiperdex.com.
Who owns hiperdex.com?
The registry did not return a person or a company for hiperdex.com. RDAP often redacts the registrant. The registrar on file is Tucows Domains Inc..
Sources
- RDAP source https://rdap.verisign.com/com/v1/domain/hiperdex.com at 2026-10-30T13:57:45Z
- DNS source 1.1.1.1:53 at 2026-10-30T13:57:45Z
- TLS source tls:443 at 2026-10-30T13:57:45Z
- HTTP source https://hiperdex.com/ at 2026-10-30T13:57:45Z
- Tech source wappalyzergo at 2026-10-30T13:57:45Z
- Geo source db-ip at 2026-10-30T13:57:45Z
- Safety source family DNS and local lists at 2026-10-30T13:57:45Z
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.