SSL Check WHOIS
Dashboard / Security Report

parco.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.

parco.co.jp: SSL/TLS grade A+ (HTTPS Monitor)parco.co.jpA+
IPv6: no public AAAA record — the domain is reachable over IPv4 only.
All 4 endpoints share identical configuration Select an IP for owner, ASN & location
A+ 13.227.173.2 IPv4 WHOIS › A+ 13.227.173.30 IPv4 WHOIS › A+ 13.227.173.31 IPv4 WHOIS › A+ 13.227.173.59 IPv4 WHOIS ›
A+

Exceptional Security

Overall Rating
Assessed 2026-11-21 05:14 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) 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 Yes 2 years · includeSubDomains · preload
HSTS Preloading Not preloadedSubmit →
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)
parco.co.jp301 → https://parco.co.jp/ → 200 OK200 OK
www.parco.co.jp301 → https://www.parco.co.jp/ → 200 OK200 OK
  • http://parco.co.jp redirects to HTTPS.

DNS Records

As a public resolver answered for parco.co.jp. Looked up 2026-11-21 05:14 UTC · 1 day ago

TypeRecords
A
AAAA None
NS
ns-1434.awsdns-51.org ns-1623.awsdns-10.co.uk ns-436.awsdns-54.com ns-816.awsdns-38.net
MX
10 mail3.parco.co.jp
SPF None

Certificate Identity

Common Nameparco.co.jp
Alt Names *.parco.co.jp parco.co.jp
IssuerCN=Cybertrust Japan SureServer CA G4, O="Cybertrust Japan Co., Ltd.", C=JP
Validity 2026-03-01 to 2027-03-31 (129 days remaining)
KeyRSA 2048 bits (sha256RSA)
Serial Number0DEF5DEDB65DAC353ACB81FC1B53AC7319912F06
SHA256 Fingerprint 98c0d56a9b0175a79623d5419584d80fabfe9fc7b90c415af34bb02e3f63d535
Pin SHA256HgSK0/kGczezmnbXrV+tCuUoZ9EpvAs5m+08nx1JalY=

Certificate Properties

Type OV Organization Validated
Cert Transparency Yes (SCT)
OCSP Must Staple No
Revocation Good (not revoked) OCSP: http://ssocsp.cybertrust.ne.jp/OcspServer CRL: http://crl.cybertrust.ne.jp/SureServer/ovcag4/cdp.crl
DNS CAA No (missing)
Trusted By Yes Mozilla · Apple · Android · Java · Windows
Name Match Yes
Validity Period 395 days (maximum 398 days for certificates issued then)
Chain IssuesNone

Trust Chain Architecture

End-Entity Certificate
CN=*.parco.co.jp, O="PARCO DIGITAL MARKETING CO.,LTD.", L=Shibuya, S=Tokyo, C=JP (Issuer: CN=Cybertrust Japan SureServer CA G4, O="Cybertrust Japan Co., Ltd.", C=JP)
Intermediate CA
CN=Cybertrust Japan SureServer CA G4, O="Cybertrust Japan Co., Ltd.", C=JP (Issuer: OU=Security Communication RootCA2, O="SECOM Trust Systems CO.,LTD.", C=JP)
Root Certificate
OU=Security Communication RootCA2, O="SECOM Trust Systems CO.,LTD.", C=JP (Issuer: OU=Security Communication RootCA2, O="SECOM Trust Systems CO.,LTD.", C=JP)

TLS History & Relations

Everything our scans have seen for parco.co.jp, first seen 2026-11-18; current certificate since 2026-11-18.

Certificates served

Certificate (SHA-256)IssuerValidServed
98c0d56a9b0175a7… current Cybertrust Japan SureServer CA G42026-03-01 → 2027-03-312026-11-18 → 2026-11-21

Addresses

AddressCertificateSeen
13.227.173.2 98c0d56a9b0175a7… 2026-11-18 → 2026-11-21
13.227.173.30 98c0d56a9b0175a7… 2026-11-18 → 2026-11-21
13.227.173.31 98c0d56a9b0175a7… 2026-11-18 → 2026-11-21
13.227.173.59 98c0d56a9b0175a7… 2026-11-18 → 2026-11-21

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

Since → last checked (UTC)GradeTLSCertificatesAddresses
2026-11-18 14:15 → 2026-11-21 05:14A+TLS 1.3 98c0d56a9b0175a7… 13.227.173.2, 13.227.173.30, 13.227.173.31, 13.227.173.59

Other hosts seen on the same addresses