idmx.io
Add this badge to your site
Shows this report's grade and links back to it. It is read from the stored report, never a new scan; a report older than 30 days also shows the month it was checked.
IPv6: no public AAAA record — the domain is reachable over IPv4 only.
Grade Breakdown
Protocol Support 95%
Key Exchange 90%
Cipher Strength 100%
Certificate 100%
Site Access: HTTP and HTTPS
What a visitor typing each address gets, and where its redirects end (up to 5 are followed), as seen from our scanner.
| Host | http:// (port 80) | https:// (port 443) |
|---|---|---|
| idmx.io | 200 OK (unencrypted) | 200 OK |
| www.idmx.io | 200 OK (unencrypted) | 200 OK |
- http://idmx.io answers without redirecting to HTTPS: visitors who type the address without https:// get an unencrypted page.
- http://www.idmx.io answers without redirecting to HTTPS.
DNS Records
As a public resolver answered for idmx.io. Looked up 2026-11-22 23:52 UTC · today
| Type | Records |
|---|---|
| A | |
| AAAA | None |
| NS | ns1031.ui-dns.biz ns1079.ui-dns.com ns1102.ui-dns.de ns1110.ui-dns.org |
| MX | 1 aspmx.l.google.com 5 alt1.aspmx.l.google.com 5 alt2.aspmx.l.google.com 5 alt3.aspmx.l.google.com 5 alt4.aspmx.l.google.com |
| SPF | v=spf1 include:_spf-us.ionos.com ~all |
Certificate Identity
| Common Name | idmx.io |
| Alt Names | idmx.io www.idmx.io |
| Issuer | CN=YE1, O=Let's Encrypt, C=US |
| Validity | 2026-10-27 to 2027-01-25 (63 days remaining) |
| Key | ECDSA 256 bits (sha384ECDSA) |
| Serial Number | 05B650B1042846986E454E7066DC2FAEDB3E |
| SHA256 Fingerprint | 1b8b650612f21626aa3945de902b9b4f505c1c289bb0da011805bf839bfa5240 |
| Pin SHA256 | EeOJpK4btHHsigdqE/ScZ01CsKCbXlLEd18GGj8sY7w= |
Certificate Properties
| Type | DV Domain Validated |
| Cert Transparency | Yes (SCT) |
| OCSP Must Staple | No |
| Revocation | Good (not revoked) CRL: http://ye1.c.lencr.org/63.crl No OCSP responder — revocation is published via CRL only (as CA/B Forum rules now allow). |
| DNS CAA | No (missing) |
| Trusted By | Yes Mozilla · Apple · Android · Java · Windows |
| Name Match | Yes |
| Validity Period | 90 days (maximum 200 days for certificates issued then) |
| Chain Issues | None |
Protocol Configuration
Supported Protocols
TLS 1.3
TLS 1.2
TLS 1.1
TLS 1.0
SSL 3
SSL 2
Negotiated Cipher
TLS_AES_256_GCM_SHA384
Protocol Details
| Connection | |
| ALPN | http/1.1 |
| SNI Required | Yes |
| Supported Named Groups | x25519 secp256r1 x448 secp521r1 secp384r1 ffdhe2048 ffdhe3072 (server preference order) |
| Post-Quantum Key Exchange | No (no hybrid ML-KEM group such as X25519MLKEM768) |
| HTTP/3 (QUIC) | No |
| Encrypted Client Hello | No |
| Security Features | |
| Forward Secrecy | Yes (ECDHE / DHE) |
| Downgrade Prevention | Yes (legacy TLS disabled) |
| Secure Renegotiation | Supported (RFC 5746) |
| Extended Master Secret | Yes (RFC 7627) |
| OCSP Stapling | No (certificate has no OCSP responder) |
| HSTS | No |
| HSTS Preloading | N/A (HSTS not enabled) |
| Security Checks | |
| BEAST attack | Mitigated |
| POODLE (SSLv3) | No (SSL 3 not supported) |
| POODLE (TLS) | No |
| RC4 | No |
| SSL/TLS Compression | No (not supported by .NET TLS stack) |
| Heartbleed | Not tested |
Cipher Suite Analysis
| Cipher Suite | Hex | Key Exchange | FS | Bits | Strength |
|---|---|---|---|---|---|
| # TLS 1.3 (server-preferred order) | |||||
| TLS_AES_128_GCM_SHA256 | 0x1301 | ECDHE | FS | 128 | Secure |
| TLS_AES_256_GCM_SHA384 | 0x1302 | ECDHE | FS | 256 | Secure |
| TLS_CHACHA20_POLY1305_SHA256 | 0x1303 | ECDHE | FS | 256 | Secure |
| # TLS 1.2 (server-preferred order) | |||||
| TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384 | 0xC02C | ECDHE | FS | 256 | Secure |
| TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 | 0xC02B | ECDHE | FS | 128 | Secure |
| TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305_SHA256 | 0xCCA9 | ECDHE | FS | 256 | Secure |
Handshake Simulation
| Client | Protocol | Cipher Suite | Result |
|---|---|---|---|
| Chrome 120 / Win 11 | TLS 1.3 | TLS_AES_256_GCM_SHA384 | Success |
| Chrome 80 / Win 10 | TLS 1.3 | TLS_AES_256_GCM_SHA384 | Success |
| Firefox 115 / Win 10 | TLS 1.3 | TLS_AES_256_GCM_SHA384 | Success |
| iOS 17 / Safari | TLS 1.3 | TLS_CHACHA20_POLY1305_SHA256 | Success |
| macOS 14 / Safari | TLS 1.3 | TLS_AES_256_GCM_SHA384 | Success |
| Android 14 | TLS 1.3 | TLS_AES_128_GCM_SHA256 | Success |
| Chrome 69 / Win 7 | TLS 1.2 | TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384 | Success |
| Chrome 49 / XP SP3 | TLS 1.2 | TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384 | Success |
| IE 11 / Win 10 | TLS 1.2 | TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384 | Success |
| IE 11 / Win 7 | TLS 1.2 | TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384 | Success |
| Android 9.0 | TLS 1.2 | TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384 | Success |
| Android 7.0 | TLS 1.2 | TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384 | Success |
| Android 5.0 | TLS 1.2 | TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384 | Success |
| Android 4.4.2 | TLS 1.2 | TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384 | Success |
| Java 11 | TLS 1.2 | TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384 | Success |
| Java 8u121 | TLS 1.2 | TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384 | Success |
| Android 4.0.4 | - | - | No |
| Android 4.1.1 | - | - | No |
| Baidu Jan 2015 | - | - | No |
| Java 6 | - | - | No |
* Simulated based on server's supported protocols and cipher configuration.
Trust Chain Architecture
End-Entity Certificate
CN=idmx.io (Issuer: CN=YE1, O=Let's Encrypt, C=US)
Intermediate CA
CN=YE1, O=Let's Encrypt, C=US (Issuer: CN=Root YE, O=ISRG, C=US)
Intermediate CA
CN=Root YE, O=ISRG, C=US (Issuer: CN=ISRG Root X2, O=Internet Security Research Group, C=US)
Root Certificate
CN=ISRG Root X2, O=Internet Security Research Group, C=US (Issuer: CN=ISRG Root X2, O=Internet Security Research Group, C=US)
Certificates & Relations
The current state of idmx.io as of our latest scan; certificate changed 2026-11-22.
Certificates served
| Certificate (SHA-256) | Issuer | Valid |
|---|---|---|
| 1b8b650612f21626… | YE1 | 2026-10-27 → 2027-01-25 |
Addresses
| Address | AS |
|---|---|
| 64.227.173.24 | AS14061 DIGITALOCEAN-ASN - DigitalOcean, LLC |