SSL Check WHOIS
Dashboard / Security Report

ticket.akb48.co.jp

Overall grade based on: IPv4: 4 of 4 complete · IPv6: 0 of 4 complete, 4 pending — IPv6 results are added below when their scan finishes; they do not count until then.
IPv6 scan in progress
2600:9000:2450:4000:4:2718:cb80:93a1 IPv6 · Pending: IPv6 scan not started yet (it runs when the report is opened, or via POST /api/ssl-check/{domain}/ipv6).
2600:9000:2450:5e00:4:2718:cb80:93a1 IPv6 · Pending: IPv6 scan not started yet (it runs when the report is opened, or via POST /api/ssl-check/{domain}/ipv6).
2600:9000:2450:6200:4:2718:cb80:93a1 IPv6 · Pending: IPv6 scan not started yet (it runs when the report is opened, or via POST /api/ssl-check/{domain}/ipv6).
2600:9000:2450:6a00:4:2718:cb80:93a1 IPv6 · Pending: IPv6 scan not started yet (it runs when the report is opened, or via POST /api/ssl-check/{domain}/ipv6).

The IPv4 report below is complete. IPv6 results will be added to this page automatically when the scan finishes.

All 4 endpoints share identical configuration Select an IP for owner, ASN & location
A+ 18.164.52.105 IPv4 WHOIS › A+ 18.164.52.47 IPv4 WHOIS › A+ 18.164.52.62 IPv4 WHOIS › A+ 18.164.52.82 IPv4 WHOIS ›
A+

Exceptional Security

Overall Rating
Assessed 2026-11-09 23:12 UTC

Grade Breakdown

Protocol Support 95%
Key Exchange 90%
Cipher Strength 100%
Certificate 100%

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) Yes (advertised)
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 Yes
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)
ticket.akb48.co.jp301 → https://ticket.akb48.co.jp/ → … → https://akb48.zaiko.io/en → 200 OK302 → https://akb48.zaiko.io/ → … → https://akb48.zaiko.io/en → 200 OK
  • http://ticket.akb48.co.jp redirects to HTTPS.
  • https://ticket.akb48.co.jp forwards visitors to akb48.zaiko.io, a different site. View its report ›

DNS Records

As a public resolver answered for ticket.akb48.co.jp and its domain akb48.co.jp. Looked up 2026-11-09 23:12 UTC · 7 days ago

TypeRecords
ticket.akb48.co.jp
A
AAAA
MX None
SPF None
akb48.co.jp
A None
AAAA None
NS
01.dnsv.jp 02.dnsv.jp 03.dnsv.jp 04.dnsv.jp
MX
10 dmail.kagoya.net
SPF
v=spf1 +ip4:210.134.58.84 +ip4:111.171.215.117 +ip4:111.171.214.127 include:spf1.siella.jp include:webcas.net include:spf.repica.jp include:em3429.akb48.co.jp include:asp.cuenote.jp include:spf.bmv.jp ~all

Certificate Identity

Common Nameticket.akb48.co.jp
Alt Names zaiko.io zaiko.kr zaiko.tw zaiko.hk *.zaiko.hk *.zaiko.tw *.zaiko.sg zaikomail.com ticket.akb48.co.jp ticket.akb48-group.com zaiko.sg *.zaiko.io *.zaikomail.com *.zaiko.kr
IssuerCN=Amazon RSA 2048 M01, O=Amazon, C=US
Validity 2026-10-10 to 2027-04-25 (159 days remaining)
KeyRSA 2048 bits (sha256RSA)
Serial Number0931B923F6442C5B82D1F121955B8664
SHA256 Fingerprint df71b0ce0e8da91d580871aac548571c261f3a235f24d81595efda6223c0ae4d
Pin SHA256BtPYyB5sH9UD1dTkf5Ayld+wVInhzEXe9CC1wTfJwG4=

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=zaiko.io (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 ticket.akb48.co.jp, first seen 2026-05-25; current certificate since 2026-11-09.

Certificates served

Certificate (SHA-256)IssuerValidServed
df71b0ce0e8da91d… current Amazon RSA 2048 M012026-10-10 → 2027-04-252026-11-09

Addresses

AddressCertificateSeen
18.164.52.47 df71b0ce0e8da91d… 2026-11-09
18.164.52.62 df71b0ce0e8da91d… 2026-11-09
18.164.52.82 df71b0ce0e8da91d… 2026-11-09
18.164.52.105 df71b0ce0e8da91d… 2026-11-09

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

Since → last checked (UTC)GradeTLSCertificatesAddresses
2026-11-09 23:12A+TLS 1.3 df71b0ce0e8da91d… 18.164.52.47, 18.164.52.62, 18.164.52.82, 18.164.52.105

Other domains on the same certificate

Other hosts seen on the same addresses