aplus.co.jp has no HTTPS: Port 443 accepts connections on all 2 IPv4 addresses, but no TLS handshake is completed: there is no working HTTPS. The site is served on www.aplus.co.jp; this is its report. (aplus.co.jp checked 2026-10-26 00:43 UTC)
www.aplus.co.jp
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.
All 2 endpoints share identical configuration Select an IP for owner, ASN & location
A+ 2.17.197.122 IPv4 WHOIS › A+ 2.17.197.177 IPv4 WHOIS › 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_256_GCM_SHA384
Protocol Details
| Connection | |
| ALPN | h2 http/1.1 |
| SNI Required | Yes |
| Supported Named Groups | X25519MLKEM768 x25519 secp256r1 (server preference order) |
| Post-Quantum Key Exchange | Yes 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 | Yes |
| HSTS | Unknown (the HTTPS request to this IP failed) |
| 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 | |||||
| TLS_AES_256_GCM_SHA384 | 0x1302 | ECDHE | FS | 256 | Secure |
| TLS_CHACHA20_POLY1305_SHA256 | 0x1303 | ECDHE | FS | 256 | Secure |
| TLS_AES_128_GCM_SHA256 | 0x1301 | ECDHE | FS | 128 | Secure |
| # TLS 1.2 | |||||
| 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 |
| TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 | 0xC030 | ECDHE | FS | 256 | Secure |
| TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 | 0xC02F | ECDHE | FS | 128 | Secure |
| TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256 | 0xCCA8 | 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.
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) |
|---|---|---|
| www.aplus.co.jp | No answer (timed out) | No answer (timed out) |
| aplus.co.jp | 400 Bad Request (unencrypted) | TLS handshake failed |
- aplus.co.jp has no working HTTPS (TLS handshake failed): visitors who type that name do not reach the HTTPS site.
DNS Records
As a public resolver answered for www.aplus.co.jp and its domain aplus.co.jp. Looked up 2026-11-19 01:36 UTC · 3 days ago
| Type | Records |
|---|---|
| www.aplus.co.jp | |
| A | |
| AAAA | None |
| MX | None |
| SPF | None |
| aplus.co.jp | |
| A | |
| AAAA | None |
| NS | ns008-uvv0otkumj35baqs.u.d-53.info ns008-uvv0otkumj35baqs.u.d-53.jp ns008-uvv0otkumj35baqs.u.d-53.net |
| MX | 10 mx.securemx.jp |
| SPF | v=spf1 ip4:221.114.168.35 ip4:202.221.147.66 ip4:203.180.85.64/26 ip4:83.166.79.203 ip4:202.22.171.21 include:tis01-spf.mrs.mpub.ne.jp include:www.digi-mel.jp include:smp.ne.jp include:spf.securemx.jp include:spf.tsp-service.smtps.jp include:_spf.salesforce.com ~all |
Certificate Identity
| Common Name | www.aplus.co.jp |
| Alt Names | www.aplus.co.jp www.aplusfinancial.co.jp www.bankit.jp www.gaica.jp |
| Issuer | CN=DigiCert Global G3 TLS ECC SHA384 2020 CA1, O=DigiCert Inc, C=US |
| Validity | 2026-08-20 to 2027-03-06 (104 days remaining) |
| Key | ECDSA 256 bits (sha384ECDSA) |
| Serial Number | 02D717ACF0EE51E6D0280DA8792CBA98 |
| SHA256 Fingerprint | 158cf6a2422c30891f30b2f0812f44391c8bc7be4b4dfb63a2aa9d3b7d61f5f3 |
| Pin SHA256 | h+yrLOl5ZwxZZsFhUact8wfyQm1P2Se0g+arpwPjMLQ= |
Certificate Properties
| Type | EV Extended Validation |
| Cert Transparency | Yes (SCT) |
| OCSP Must Staple | No |
| Revocation | Good (not revoked) OCSP: http://ocsp.digicert.com CRL: http://crl3.digicert.com/DigiCertGlobalG3TLSECCSHA3842020CA1-2.crl |
| DNS CAA | No (missing) |
| Trusted By | Yes Mozilla · Apple · Android · Java · Windows |
| Name Match | Yes |
| Validity Period | 199 days (maximum 200 days for certificates issued then) |
| Chain Issues | None |
Trust Chain Architecture
End-Entity Certificate
CN=www.aplus.co.jp, O="APLUS Co., Ltd.", L=Chuo-ku, S=Tokyo, C=JP, SERIALNUMBER=1200-01-137521, businessCategory=Private Organization, jurisdictionCountryName=JP (Issuer: CN=DigiCert Global G3 TLS ECC SHA384 2020 CA1, O=DigiCert Inc, C=US)
Intermediate CA
CN=DigiCert Global G3 TLS ECC SHA384 2020 CA1, O=DigiCert Inc, C=US (Issuer: CN=DigiCert Global Root G3, OU=www.digicert.com, O=DigiCert Inc, C=US)
Root Certificate
CN=DigiCert Global Root G3, OU=www.digicert.com, O=DigiCert Inc, C=US (Issuer: CN=DigiCert Global Root G3, OU=www.digicert.com, O=DigiCert Inc, C=US)
Certificates & Relations
The current state of www.aplus.co.jp as of our latest scan; certificate changed 2026-11-19.
Certificates served
| Certificate (SHA-256) | Issuer | Valid |
|---|---|---|
| 158cf6a2422c3089… | DigiCert Global G3 TLS ECC SHA384 2020 CA1 | 2026-08-20 → 2027-03-06 |
Addresses
| Address | AS |
|---|---|
| 2.17.197.122 | — |
| 2.17.197.177 | — |
Other domains on the same certificate
- aplusfinancial.co.jp 1 name
- bankit.jp 1 name
- gaica.jp 1 name
Other hosts on the same addresses
api-realm5.sephora.eu boatatvrenewals.polkcountyiowa.gov brandedcontentbe.spaargids.be community.java.net databaseworld.com developer.api.walmart.com federos.com gaappeals.polkcountyiowa.gov gmmediacenter.com gmmediaplatform.com guide-epargne.be java-champions.java.net markie-awards.com mobiletravelapi-stage.united.com mystatus.united.com oraclecloudworld.com playground.qmusic.nl securasset.lu secure.dove.ph secure.knorr.com.ar secure.maxadventure.ru selectiondevaleurs.fr spring-gds.com unitedcorporatepreferred.com votreallure.ca webform2.consorsfinanz.de webinars.shalinamedspace.com www.badboys-movie.jp www.cartedor.co.uk www.cleanipedia.at www.cleanipedia.in www.lifebuoy.com.sg www.lovehomeandplanet.com www.memri.org www.moat.com www.netsuite.com www.netsuite.eu www.omomatic.com www.swalayankita.com www.tarjetaplaystation.com