mikocon.com
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
OfflineSafeSSL: -646 days left13 years oldTranco #115711
35
mikocon.com was registered on 21 Jul 2013 via GoDaddy.com, LLC and the registry expiry is 21 Jul 2027. WHOIS data came from RDAP at https://rdap.verisign.com/com/v1/domain/mikocon.com.
mikocon.com publishes 2 nameservers. DNSSEC is not signed.
mikocon.com has 1 IPv4 address (94.102.49.69). The geolocation database places 94.102.49.69 in Amsterdam, The Netherlands.
The TLS certificate from R11 is not valid (TLS 1.2).
No safety warning was recorded for mikocon.com in the checks that ran.
Domain · RDAP/WHOIS
mikocon.com was registered on 21 Jul 2013 via GoDaddy.com, LLC. The registry returned 4 status values and 2 nameservers from https://rdap.verisign.com/com/v1/domain/mikocon.com.
| Registered | since 21 Jul 2013 |
|---|---|
| Created | 21 July 2013 |
| Updated | 9 June 2026 |
| Expires | 21 July 2027 |
| Registrar | GoDaddy.com, LLC |
| Status | client delete prohibited, client renew prohibited, client transfer prohibited, client update prohibited |
| Nameservers | ns57.domaincontrol.com, ns58.domaincontrol.com |
| DNSSEC | no |
| Source | https://rdap.verisign.com/com/v1/domain/mikocon.com |
mikocon.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.
mikocon.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.
mikocon.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.
mikocon.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 ns57.domaincontrol.com is published for mikocon.com in the registration record from https://rdap.verisign.com/com/v1/domain/mikocon.com.
Nameserver ns58.domaincontrol.com is published for mikocon.com in the registration record from https://rdap.verisign.com/com/v1/domain/mikocon.com.
DNS
mikocon.com has 1 address record, 1 mail exchanger and 2 nameservers, measured at 1.1.1.1:53.
| A | 94.102.49.69 |
|---|---|
| AAAA | — |
| NS | ns57.domaincontrol.com, ns58.domaincontrol.com |
| MX | mikocon.com (5) |
| SPF | present |
| DMARC | absent |
| CAA | — |
| Wildcard | off |
| DNSSEC | not signed |
| Resolver | 1.1.1.1:53 |
The SPF text record at mikocon.com is "v=spf1 include:spf.mail.qq.com ~all".
IPv4 address 94.102.49.69 answers for mikocon.com at resolver 1.1.1.1:53.
Mail exchanger mikocon.com has preference 5.
Hosting and geo
mikocon.com is placed in Amsterdam, The Netherlands by the local geolocation database (db-ip).
| Address | 94.102.49.69 |
|---|---|
| Country | The Netherlands |
| City | Amsterdam |
| Source | db-ip |
SSL/TLS
The certificate for mikocon.com is not valid, with -646 days left and 1 subject alternative name. Source: tls:443.
| Issuer | R11 |
|---|---|
| Subject | mikocon.com |
| Valid from | 25 October 2024 |
| Valid until | 23 January 2025 |
| Days left | -646 |
| SAN count | 1 |
| Protocol | TLS 1.2 |
| Source | tls:443 |
Subject alternative names: mikocon.com.
Validation result: certificate did not validate
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 |
|---|
Get "https://mikocon.com/": tls: failed to verify certificate: x509: certificate has expired or is not yet valid: current time 2026-10-30T14:04:00Z is after 2025-01-23T04:37:18Z
Security
Family DNS for mikocon.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 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
- October 2026: geo city changed from empty to Amsterdam.
- October 2026: geo country changed from empty to The Netherlands.
Questions
Is mikocon.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 mikocon.com?
mikocon.com is placed in Amsterdam, The Netherlands.
When does mikocon.com expire?
mikocon.com expires on 21 July 2027 according to https://rdap.verisign.com/com/v1/domain/mikocon.com.
Who owns mikocon.com?
The registry did not return a person or a company for mikocon.com. RDAP often redacts the registrant. The registrar on file is GoDaddy.com, LLC.
Sources
- RDAP source https://rdap.verisign.com/com/v1/domain/mikocon.com at 2026-10-30T14:04:00Z
- DNS source 1.1.1.1:53 at 2026-10-30T14:04:00Z
- TLS source tls:443 at 2026-10-30T14:04:00Z
- HTTP source https://mikocon.com/ at 2026-10-30T14:04:00Z
- Tech source not available at 2026-10-30T14:04:00Z
- Geo source db-ip at 2026-10-30T14:04:00Z
- Safety source family DNS and local lists at 2026-10-30T14:04:00Z
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.