mycubex.com
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
OfflineSafe16 years oldTranco #714742
30
mycubex.com was registered on 23 Dec 2009 via GoDaddy.com, LLC and the registry expiry is 23 Dec 2027. WHOIS data came from RDAP at https://rdap.verisign.com/com/v1/domain/mycubex.com.
mycubex.com publishes 2 nameservers. DNSSEC is not signed.
mycubex.com has 1 IPv4 address (20.112.76.89). The geolocation database places 20.112.76.89 in Quincy, United States.
No safety warning was recorded for mycubex.com in the checks that ran.
Domain · RDAP/WHOIS
mycubex.com was registered on 23 Dec 2009 via GoDaddy.com, LLC. The registry returned 4 status values and 2 nameservers from https://rdap.verisign.com/com/v1/domain/mycubex.com.
| Registered | since 23 Dec 2009 |
|---|---|
| Created | 23 December 2009 |
| Updated | 24 December 2025 |
| Expires | 23 December 2027 |
| Registrar | GoDaddy.com, LLC |
| Status | client delete prohibited, client renew prohibited, client transfer prohibited, client update prohibited |
| Nameservers | ns27.domaincontrol.com, ns28.domaincontrol.com |
| DNSSEC | no |
| Source | https://rdap.verisign.com/com/v1/domain/mycubex.com |
mycubex.com 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.
mycubex.com 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.
mycubex.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.
mycubex.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 ns27.domaincontrol.com is published for mycubex.com in the registration record from https://rdap.verisign.com/com/v1/domain/mycubex.com.
Nameserver ns28.domaincontrol.com is published for mycubex.com in the registration record from https://rdap.verisign.com/com/v1/domain/mycubex.com.
DNS
mycubex.com has 1 address record, 2 mail exchangers and 2 nameservers, measured at 1.1.1.1:53.
| A | 20.112.76.89 |
|---|---|
| AAAA | — |
| NS | ns27.domaincontrol.com, ns28.domaincontrol.com |
| MX | smtp.secureserver.net (0) GoDaddy, mailstore1.secureserver.net (10) GoDaddy |
| SPF | absent |
| DMARC | absent |
| CAA | — |
| Wildcard | off |
| DNSSEC | not signed |
| Resolver | 1.1.1.1:53 |
IPv4 address 20.112.76.89 answers for mycubex.com at resolver 1.1.1.1:53.
Mail exchanger smtp.secureserver.net has preference 0. The host is recognised as GoDaddy.
Mail exchanger mailstore1.secureserver.net has preference 10. The host is recognised as GoDaddy.
Hosting and geo
mycubex.com is placed in Quincy, United States by the local geolocation database (db-ip).
| Address | 20.112.76.89 |
|---|---|
| Country | United States |
| City | Quincy |
| Source | db-ip |
SSL/TLS
No TLS certificate was read for mycubex.com on port 443.
| Available | no |
|---|---|
| Source | tls:443 |
dial tcp 20.112.76.89: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 mycubex.com 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 0 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 5 of 5. Five points at one year, two points at 30 days.
Change history
- October 2026: geo city changed from empty to Quincy.
- October 2026: geo country changed from empty to United States.
Questions
Is mycubex.com 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 mycubex.com?
mycubex.com is placed in Quincy, United States.
When does mycubex.com expire?
mycubex.com expires on 23 December 2027 according to https://rdap.verisign.com/com/v1/domain/mycubex.com.
Who owns mycubex.com?
The registry did not return a person or a company for mycubex.com. RDAP often redacts the registrant. The registrar on file is GoDaddy.com, LLC.
Sources
- RDAP source https://rdap.verisign.com/com/v1/domain/mycubex.com at 2026-10-30T14:05:33Z
- DNS source 1.1.1.1:53 at 2026-10-30T14:05:33Z
- TLS source tls:443 at 2026-10-30T14:05:33Z
- HTTP source https://mycubex.com/ at 2026-10-30T14:05:33Z
- Tech source not available at 2026-10-30T14:05:33Z
- Geo source db-ip at 2026-10-30T14:05:33Z
- Safety source family DNS and local lists at 2026-10-30T14:05:33Z
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.