SSL Check WHOIS
Dashboard / Security Report

mai-ko.com

Overall grade based on: IPv4: 4 of 4 complete · IPv6: 4 of 4 complete
All 8 endpoints share identical configuration Select an IP for owner, ASN & location
A+ 52.222.154.58 IPv4 WHOIS › A+ 52.222.154.59 IPv4 WHOIS › A+ 52.222.154.68 IPv4 WHOIS › A+ 52.222.154.82 IPv4 WHOIS › A+ 2600:9000:218e:0:19:ee9b:4100:93a1 IPv6 WHOIS › A+ 2600:9000:218e:3200:19:ee9b:4100:93a1 IPv6 WHOIS › A+ 2600:9000:218e:3400:19:ee9b:4100:93a1 IPv6 WHOIS › A+ 2600:9000:218e:6200:19:ee9b:4100:93a1 IPv6 WHOIS ›

Protocol Configuration

Supported Protocols

TLS 1.3
TLS 1.2
TLS 1.1
TLS 1.0
SSL 3
SSL 2

Negotiated Cipher

TLS_AES_128_GCM_SHA256

Protocol Details

Connection
ALPN h2 http/1.1
SNI Required Yes
Supported Named Groups X25519MLKEM768 SecP256r1MLKEM768 x25519 secp256r1 secp384r1 (server preference order)
Post-Quantum Key Exchange Yes X25519MLKEM768, SecP256r1MLKEM768
HTTP/3 (QUIC) No
Encrypted Client Hello No
Security Features
Forward SecrecyYes (ECDHE / DHE)
Scan Coverage Incomplete no answer in time for: key exchange groups — shown as unknown, not as unsupported
Downgrade Prevention Yes (legacy TLS disabled)
Secure Renegotiation Supported (RFC 5746)
Extended Master Secret Yes (RFC 7627)
OCSP Stapling No
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 CompressionNo (not supported by .NET TLS stack)
HeartbleedNot tested

Cipher Suite Analysis

Cipher SuiteHexKey ExchangeFSBitsStrength
# TLS 1.3
TLS_AES_128_GCM_SHA2560x1301ECDHEFS128Secure
TLS_AES_256_GCM_SHA3840x1302ECDHEFS256Secure
TLS_CHACHA20_POLY1305_SHA2560x1303ECDHEFS256Secure
# TLS 1.2
TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA2560xC02FECDHEFS128Secure
TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA3840xC030ECDHEFS256Secure
TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA2560xCCA8ECDHEFS256Secure

Handshake Simulation

ClientProtocolCipher SuiteResult
Chrome 120 / Win 11TLS 1.3TLS_AES_256_GCM_SHA384Success
Chrome 80 / Win 10TLS 1.3TLS_AES_256_GCM_SHA384Success
Firefox 115 / Win 10TLS 1.3TLS_AES_256_GCM_SHA384Success
iOS 17 / SafariTLS 1.3TLS_CHACHA20_POLY1305_SHA256Success
macOS 14 / SafariTLS 1.3TLS_AES_256_GCM_SHA384Success
Android 14TLS 1.3TLS_AES_128_GCM_SHA256Success
Chrome 69 / Win 7TLS 1.2TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256Success
Chrome 49 / XP SP3TLS 1.2TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256Success
IE 11 / Win 10TLS 1.2TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256Success
IE 11 / Win 7TLS 1.2TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256Success
Android 9.0TLS 1.2TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256Success
Android 7.0TLS 1.2TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256Success
Android 5.0TLS 1.2TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256Success
Android 4.4.2TLS 1.2TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256Success
Java 11TLS 1.2TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256Success
Java 8u121TLS 1.2TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256Success
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.

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.

Hosthttp:// (port 80)https:// (port 443)
mai-ko.com301 → https://mai-ko.com/ → 200 OK200 OK
www.mai-ko.com301 → https://www.mai-ko.com/ → … → https://mai-ko.com/ → 200 OK301 → https://mai-ko.com/ → 200 OK
  • http://mai-ko.com redirects to HTTPS.

DNS Records

As a public resolver answered for mai-ko.com. Looked up 2026-11-06 00:48 UTC · 11 days ago

TypeRecords
A
AAAA
NS None
MX
10 sv2237.xserver.jp
SPF
v=spf1 include:spf.sender.xserver.jp include:_spf.google.com -all

Certificate Identity

Common Namemai-ko.com
Alt Names mai-ko.com www.mai-ko.com
IssuerCN=Amazon RSA 2048 M01, O=Amazon, C=US
Validity 2026-10-09 to 2027-04-24 (158 days remaining)
KeyRSA 2048 bits (sha256RSA)
Serial Number0E88BC77AC1BD463E9E99E44427A3FBB
SHA256 Fingerprint 94bc0b21935080ade3dba07aebda44ee3da1f09109a63f9547461a88d5713824
Pin SHA256pu3A8tH50dUag/gi5D5p8sIkx4uXVeMt3atNdgNosgo=

Certificate Properties

Type DV
Cert Transparency Yes (SCT)
OCSP Must Staple No
Revocation Good (not revoked) OCSP: http://ocsp.r2m01.amazontrust.com CRL: http://crl.r2m01.amazontrust.com/r2m01.crl
DNS CAA No (missing)
Trusted By Yes Mozilla · Apple · Android · Java · Windows
Name Match Yes
Validity Period 198 days (maximum 200 days for certificates issued then)
Chain IssuesNone

Trust Chain Architecture

End-Entity Certificate
CN=mai-ko.com (Issuer: CN=Amazon RSA 2048 M01, O=Amazon, C=US)
Intermediate CA
CN=Amazon RSA 2048 M01, O=Amazon, C=US (Issuer: CN=Amazon Root CA 1, O=Amazon, C=US)
Root Certificate
CN=Amazon Root CA 1, O=Amazon, C=US (Issuer: CN=Amazon Root CA 1, O=Amazon, C=US)

TLS History & Relations

Everything our scans have seen for mai-ko.com, first seen 2026-11-06; current certificate since 2026-11-06.

Certificates served

Certificate (SHA-256)IssuerValidServed
94bc0b21935080ad… current Amazon RSA 2048 M012026-10-09 → 2027-04-242026-11-06

Addresses

AddressCertificateSeen
52.222.154.58 94bc0b21935080ad… 2026-11-06
52.222.154.59 94bc0b21935080ad… 2026-11-06
52.222.154.68 94bc0b21935080ad… 2026-11-06
52.222.154.82 94bc0b21935080ad… 2026-11-06
2600:9000:218e:0:19:ee9b:4100:93a1 94bc0b21935080ad… 2026-11-06
2600:9000:218e:3200:19:ee9b:4100:93a1 94bc0b21935080ad… 2026-11-06
2600:9000:218e:3400:19:ee9b:4100:93a1 94bc0b21935080ad… 2026-11-06
2600:9000:218e:6200:19:ee9b:4100:93a1 94bc0b21935080ad… 2026-11-06

TLS history (a row per change; repeated checks only extend it)

Since → last checked (UTC)GradeTLSCertificatesAddresses
2026-11-06 00:48A+TLS 1.3 94bc0b21935080ad… 52.222.154.58, 52.222.154.59, 52.222.154.68, 52.222.154.82

Other hosts seen on the same addresses