SSL Report: dbda.pcf-oin.npa.go.jp (111.111.122.37)
Assessed on:  Thu, 11 Sep 2025 11:21:15 UTC | Clear cache

Due to a recently discovered bug in Apple's code, your browser is exposed to MITM attacks. Click here for more information.

Summary
Overall Rating
A-
0
20
40
60
80
100
Certificate
 
Protocol Support
 
Key Exchange
 
Cipher Strength
 

Visit our documentation page for more information, configuration guides, and books. Known issues are documented here.
There is no support for secure renegotiation. Grade reduced to A-.  MORE INFO »
This server supports TLS 1.3.  MORE INFO »
Certificate #1: RSA 2048 bits (SHA256withRSA)
Server Key and Certificate #1
Subject dbda.pcf-oin.npa.go.jp
Fingerprint SHA256: 5268d7834c3862bb7f7cb066e89e78d454e9b861598658e401bbe77649a6d0bb
Pin SHA256: snNAqppsL+6dPmqbXKnrDzRXmF/yxEGzpE2hk1Az6T4=
Common names dbda.pcf-oin.npa.go.jp
Alternative names dbda.pcf-oin.npa.go.jp
Serial Number 38db2bcc848875f401f21e34ac37bbbe
Valid from Fri, 23 May 2025 03:25:46 UTC
Valid until Fri, 12 Jun 2026 14:59:59 UTC (expires in 9 months and 1 day)
Key RSA 2048 bits (e 65537)
Weak key (Debian) No
Issuer SECOM Passport for Web SR 3.0 CA
AIA: http://repo1.secomtrust.net/spcpp/pfw/pfwsr3ca/ca2-der.cer
Signature algorithm SHA256withRSA
Extended Validation No
Certificate Transparency Yes (certificate)
OCSP Must Staple No
Revocation information CRL, OCSP
CRL: http://repo1.secomtrust.net/spcpp/pfw/pfwsr3ca/fullcrl2.crl
OCSP: http://sr30.ocsp.secomtrust.net
Revocation status Good (not revoked)
DNS CAA No (more info)
Trusted Yes
Mozilla  Apple  Android  Java  Windows 


Additional Certificates (if supplied)
Certificates provided 2 (3039 bytes)
Chain issues None
#2
Subject SECOM Passport for Web SR 3.0 CA
Fingerprint SHA256: 59f8a94c11bcd19fd4e0f1ac4d394e37913ae5fb5862a25a8ecd167ba3b9a3a2
Pin SHA256: Rhcj0dcdOovISeMPXTWpuUDiNf1EzyxSHeMUK0lfoR8=
Valid until Thu, 16 Mar 2028 05:49:12 UTC (expires in 2 years and 6 months)
Key RSA 2048 bits (e 65537)
Issuer SECOM Trust Systems CO.,LTD. / Security Communication RootCA2
Signature algorithm SHA256withRSA


Certification Paths
Path #1: Trusted
1 Sent by server dbda.pcf-oin.npa.go.jp
Fingerprint SHA256: 5268d7834c3862bb7f7cb066e89e78d454e9b861598658e401bbe77649a6d0bb
Pin SHA256: snNAqppsL+6dPmqbXKnrDzRXmF/yxEGzpE2hk1Az6T4=

RSA 2048 bits (e 65537) / SHA256withRSA
2 Sent by server SECOM Passport for Web SR 3.0 CA
Fingerprint SHA256: 59f8a94c11bcd19fd4e0f1ac4d394e37913ae5fb5862a25a8ecd167ba3b9a3a2
Pin SHA256: Rhcj0dcdOovISeMPXTWpuUDiNf1EzyxSHeMUK0lfoR8=

RSA 2048 bits (e 65537) / SHA256withRSA
3 In trust store SECOM Trust Systems CO.,LTD. / Security Communication RootCA2   Self-signed
Fingerprint SHA256: 513b2cecb810d4cde5dd85391adfc6c2dd60d87bb736d2b521484aa47a0ebef6
Pin SHA256: M4BwmvOwlr48wqQFSBQsClIAKNsJ4st3riIGYWq2y7Q=

RSA 2048 bits (e 65537) / SHA256withRSA
Path #1: Trusted
1 Sent by server dbda.pcf-oin.npa.go.jp
Fingerprint SHA256: 5268d7834c3862bb7f7cb066e89e78d454e9b861598658e401bbe77649a6d0bb
Pin SHA256: snNAqppsL+6dPmqbXKnrDzRXmF/yxEGzpE2hk1Az6T4=

RSA 2048 bits (e 65537) / SHA256withRSA
2 Sent by server SECOM Passport for Web SR 3.0 CA
Fingerprint SHA256: 59f8a94c11bcd19fd4e0f1ac4d394e37913ae5fb5862a25a8ecd167ba3b9a3a2
Pin SHA256: Rhcj0dcdOovISeMPXTWpuUDiNf1EzyxSHeMUK0lfoR8=

RSA 2048 bits (e 65537) / SHA256withRSA
3 In trust store SECOM Trust Systems CO.,LTD. / Security Communication RootCA2   Self-signed
Fingerprint SHA256: 513b2cecb810d4cde5dd85391adfc6c2dd60d87bb736d2b521484aa47a0ebef6
Pin SHA256: M4BwmvOwlr48wqQFSBQsClIAKNsJ4st3riIGYWq2y7Q=

RSA 2048 bits (e 65537) / SHA256withRSA
Path #1: Trusted
1 Sent by server dbda.pcf-oin.npa.go.jp
Fingerprint SHA256: 5268d7834c3862bb7f7cb066e89e78d454e9b861598658e401bbe77649a6d0bb
Pin SHA256: snNAqppsL+6dPmqbXKnrDzRXmF/yxEGzpE2hk1Az6T4=

RSA 2048 bits (e 65537) / SHA256withRSA
2 Sent by server SECOM Passport for Web SR 3.0 CA
Fingerprint SHA256: 59f8a94c11bcd19fd4e0f1ac4d394e37913ae5fb5862a25a8ecd167ba3b9a3a2
Pin SHA256: Rhcj0dcdOovISeMPXTWpuUDiNf1EzyxSHeMUK0lfoR8=

RSA 2048 bits (e 65537) / SHA256withRSA
3 In trust store SECOM Trust Systems CO.,LTD. / Security Communication RootCA2   Self-signed
Fingerprint SHA256: 513b2cecb810d4cde5dd85391adfc6c2dd60d87bb736d2b521484aa47a0ebef6
Pin SHA256: M4BwmvOwlr48wqQFSBQsClIAKNsJ4st3riIGYWq2y7Q=

RSA 2048 bits (e 65537) / SHA256withRSA
Path #1: Trusted
1 Sent by server dbda.pcf-oin.npa.go.jp
Fingerprint SHA256: 5268d7834c3862bb7f7cb066e89e78d454e9b861598658e401bbe77649a6d0bb
Pin SHA256: snNAqppsL+6dPmqbXKnrDzRXmF/yxEGzpE2hk1Az6T4=

RSA 2048 bits (e 65537) / SHA256withRSA
2 Sent by server SECOM Passport for Web SR 3.0 CA
Fingerprint SHA256: 59f8a94c11bcd19fd4e0f1ac4d394e37913ae5fb5862a25a8ecd167ba3b9a3a2
Pin SHA256: Rhcj0dcdOovISeMPXTWpuUDiNf1EzyxSHeMUK0lfoR8=

RSA 2048 bits (e 65537) / SHA256withRSA
3 In trust store SECOM Trust Systems CO.,LTD. / Security Communication RootCA2   Self-signed
Fingerprint SHA256: 513b2cecb810d4cde5dd85391adfc6c2dd60d87bb736d2b521484aa47a0ebef6
Pin SHA256: M4BwmvOwlr48wqQFSBQsClIAKNsJ4st3riIGYWq2y7Q=

RSA 2048 bits (e 65537) / SHA256withRSA
Path #1: Trusted
1 Sent by server dbda.pcf-oin.npa.go.jp
Fingerprint SHA256: 5268d7834c3862bb7f7cb066e89e78d454e9b861598658e401bbe77649a6d0bb
Pin SHA256: snNAqppsL+6dPmqbXKnrDzRXmF/yxEGzpE2hk1Az6T4=

RSA 2048 bits (e 65537) / SHA256withRSA
2 Sent by server SECOM Passport for Web SR 3.0 CA
Fingerprint SHA256: 59f8a94c11bcd19fd4e0f1ac4d394e37913ae5fb5862a25a8ecd167ba3b9a3a2
Pin SHA256: Rhcj0dcdOovISeMPXTWpuUDiNf1EzyxSHeMUK0lfoR8=

RSA 2048 bits (e 65537) / SHA256withRSA
3 In trust store SECOM Trust Systems CO.,LTD. / Security Communication RootCA2   Self-signed
Fingerprint SHA256: 513b2cecb810d4cde5dd85391adfc6c2dd60d87bb736d2b521484aa47a0ebef6
Pin SHA256: M4BwmvOwlr48wqQFSBQsClIAKNsJ4st3riIGYWq2y7Q=

RSA 2048 bits (e 65537) / SHA256withRSA

Click here to expand

Configuration
Protocols
TLS 1.3 Yes
TLS 1.2 Yes
TLS 1.1 No
TLS 1.0 No
SSL 3 No
SSL 2 No


Cipher Suites
# TLS 1.3 (we could not determine if the server has a preference)
TLS_AES_256_GCM_SHA384 (0x1302)   ECDH x25519 (eq. 3072 bits RSA)   FS 256
# TLS 1.2 (suites in server-preferred order)
TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (0xc030)   ECDH secp256r1 (eq. 3072 bits RSA)   FS 256
TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (0xc02f)   ECDH secp256r1 (eq. 3072 bits RSA)   FS 128


Handshake Simulation
Android 4.4.2 RSA 2048 (SHA256)   TLS 1.2 TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384   ECDH secp256r1  FS
Android 5.0.0 RSA 2048 (SHA256)   TLS 1.2 TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256   ECDH secp256r1  FS
Android 6.0 RSA 2048 (SHA256)   TLS 1.2 > http/1.1   TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256   ECDH secp256r1  FS
Android 7.0 RSA 2048 (SHA256)   TLS 1.2 > http/1.1   TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384   ECDH secp256r1  FS
Android 8.0 RSA 2048 (SHA256)   TLS 1.2 > http/1.1   TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384   ECDH secp256r1  FS
Android 8.1 -   TLS 1.3 TLS_AES_256_GCM_SHA384   ECDH x25519  FS
Android 9.0 -   TLS 1.3 TLS_AES_256_GCM_SHA384   ECDH x25519  FS
BingPreview Jan 2015 RSA 2048 (SHA256)   TLS 1.2 TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384   ECDH secp256r1  FS
Chrome 49 / XP SP3 RSA 2048 (SHA256)   TLS 1.2 > http/1.1   TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256   ECDH secp256r1  FS
Chrome 69 / Win 7  R RSA 2048 (SHA256)   TLS 1.2 > http/1.1   TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384   ECDH secp256r1  FS
Chrome 70 / Win 10 -   TLS 1.3 TLS_AES_256_GCM_SHA384   ECDH x25519  FS
Chrome 80 / Win 10  R -   TLS 1.3 TLS_AES_256_GCM_SHA384   ECDH x25519  FS
Firefox 31.3.0 ESR / Win 7 RSA 2048 (SHA256)   TLS 1.2 TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256   ECDH secp256r1  FS
Firefox 47 / Win 7  R RSA 2048 (SHA256)   TLS 1.2 > http/1.1   TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256   ECDH secp256r1  FS
Firefox 49 / XP SP3 RSA 2048 (SHA256)   TLS 1.2 > http/1.1   TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384   ECDH secp256r1  FS
Firefox 62 / Win 7  R RSA 2048 (SHA256)   TLS 1.2 > http/1.1   TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384   ECDH secp256r1  FS
Firefox 73 / Win 10  R -   TLS 1.3 TLS_AES_256_GCM_SHA384   ECDH x25519  FS
Googlebot Feb 2018 RSA 2048 (SHA256)   TLS 1.2 TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384   ECDH secp256r1  FS
IE 11 / Win 7  R Protocol or cipher suite mismatch
IE 11 / Win 8.1  R Protocol or cipher suite mismatch
IE 11 / Win Phone 8.1  R Protocol or cipher suite mismatch
IE 11 / Win Phone 8.1 Update  R Protocol or cipher suite mismatch
IE 11 / Win 10  R RSA 2048 (SHA256)   TLS 1.2 > http/1.1   TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384   ECDH secp256r1  FS
Edge 15 / Win 10  R RSA 2048 (SHA256)   TLS 1.2 > http/1.1   TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384   ECDH secp256r1  FS
Edge 16 / Win 10  R RSA 2048 (SHA256)   TLS 1.2 > http/1.1   TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384   ECDH secp256r1  FS
Edge 18 / Win 10  R RSA 2048 (SHA256)   TLS 1.2 > http/1.1   TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384   ECDH secp256r1  FS
Edge 13 / Win Phone 10  R RSA 2048 (SHA256)   TLS 1.2 > http/1.1   TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384   ECDH secp256r1  FS
Java 8u161 RSA 2048 (SHA256)   TLS 1.2 TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384   ECDH secp256r1  FS
Java 11.0.3 -   TLS 1.3 TLS_AES_256_GCM_SHA384   ECDH secp256r1  FS
Java 12.0.1 -   TLS 1.3 TLS_AES_256_GCM_SHA384   ECDH secp256r1  FS
OpenSSL 1.0.1l  R RSA 2048 (SHA256)   TLS 1.2 TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384   ECDH secp256r1  FS
OpenSSL 1.0.2s  R RSA 2048 (SHA256)   TLS 1.2 TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384   ECDH secp256r1  FS
OpenSSL 1.1.0k  R RSA 2048 (SHA256)   TLS 1.2 TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384   ECDH secp256r1  FS
OpenSSL 1.1.1c  R -   TLS 1.3 TLS_AES_256_GCM_SHA384   ECDH x25519  FS
Safari 6 / iOS 6.0.1 Protocol or cipher suite mismatch
Safari 7 / iOS 7.1  R Protocol or cipher suite mismatch
Safari 7 / OS X 10.9  R Protocol or cipher suite mismatch
Safari 8 / iOS 8.4  R Protocol or cipher suite mismatch
Safari 8 / OS X 10.10  R Protocol or cipher suite mismatch
Safari 9 / iOS 9  R RSA 2048 (SHA256)   TLS 1.2 > http/1.1   TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384   ECDH secp256r1  FS
Safari 9 / OS X 10.11  R RSA 2048 (SHA256)   TLS 1.2 > http/1.1   TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384   ECDH secp256r1  FS
Safari 10 / iOS 10  R RSA 2048 (SHA256)   TLS 1.2 > http/1.1   TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384   ECDH secp256r1  FS
Safari 10 / OS X 10.12  R RSA 2048 (SHA256)   TLS 1.2 > http/1.1   TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384   ECDH secp256r1  FS
Safari 12.1.2 / MacOS 10.14.6 Beta  R -   TLS 1.3 TLS_AES_256_GCM_SHA384   ECDH x25519  FS
Safari 12.1.1 / iOS 12.3.1  R -   TLS 1.3 TLS_AES_256_GCM_SHA384   ECDH x25519  FS
Apple ATS 9 / iOS 9  R RSA 2048 (SHA256)   TLS 1.2 > http/1.1   TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384   ECDH secp256r1  FS
Yahoo Slurp Jan 2015 RSA 2048 (SHA256)   TLS 1.2 TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384   ECDH secp256r1  FS
YandexBot Jan 2015 RSA 2048 (SHA256)   TLS 1.2 TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384   ECDH secp256r1  FS
# Not simulated clients (Protocol mismatch)
Android 2.3.7   No SNI 2 Protocol mismatch (not simulated)
Android 4.0.4 Protocol mismatch (not simulated)
Android 4.1.1 Protocol mismatch (not simulated)
Android 4.2.2 Protocol mismatch (not simulated)
Android 4.3 Protocol mismatch (not simulated)
Baidu Jan 2015 Protocol mismatch (not simulated)
IE 6 / XP   No FS 1   No SNI 2 Protocol mismatch (not simulated)
IE 7 / Vista Protocol mismatch (not simulated)
IE 8 / XP   No FS 1   No SNI 2 Protocol mismatch (not simulated)
IE 8-10 / Win 7  R Protocol mismatch (not simulated)
IE 10 / Win Phone 8.0 Protocol mismatch (not simulated)
Java 6u45   No SNI 2 Protocol mismatch (not simulated)
Java 7u25 Protocol mismatch (not simulated)
OpenSSL 0.9.8y Protocol mismatch (not simulated)
Safari 5.1.9 / OS X 10.6.8 Protocol mismatch (not simulated)
Safari 6.0.4 / OS X 10.8.4  R Protocol mismatch (not simulated)

Click here to expand

(1) Clients that do not support Forward Secrecy (FS) are excluded when determining support for it.
(2) No support for virtual SSL hosting (SNI). Connects to the default site if the server uses SNI.
(3) Only first connection attempt simulated. Browsers sometimes retry with a lower protocol version.
(R) Denotes a reference browser or client, with which we expect better effective security.
(All) We use defaults, but some platforms do not use their best protocols and features (e.g., Java 6 & 7, older IE).
(All) Certificate trust is not checked in handshake simulation, we only perform TLS handshake.


Protocol Details
Renegotiation Unknown
BEAST attack Mitigated server-side (more info)  
POODLE (SSLv3) No, SSL 3 not supported (more info)
POODLE (TLS) No (more info)
Zombie POODLE No (more info)  
GOLDENDOODLE No (more info)  
OpenSSL 0-Length No (more info)  
Sleeping POODLE No (more info)  
Downgrade attack prevention No, TLS_FALLBACK_SCSV not supported (more info)
SSL/TLS compression No
RC4 No
Heartbeat (extension) No
Heartbleed (vulnerability) No (more info)
Ticketbleed (vulnerability) No (more info)
OpenSSL CCS vuln. (CVE-2014-0224) No (more info)
OpenSSL Padding Oracle vuln.
(CVE-2016-2107)
No (more info)
ROBOT (vulnerability) No (more info)
Forward Secrecy Yes (with most browsers)   ROBUST (more info)
ALPN Yes   http/1.1
NPN No
Session resumption (caching) Yes
Session resumption (tickets) No
OCSP stapling No
Strict Transport Security (HSTS) No
HSTS Preloading Not in: Chrome  Edge  Firefox  IE 
Public Key Pinning (HPKP) No (more info)
Public Key Pinning Report-Only No
Public Key Pinning (Static) No (more info)
Long handshake intolerance No
TLS extension intolerance No
TLS version intolerance No
Incorrect SNI alerts No
Uses common DH primes No, DHE suites not supported
DH public server param (Ys) reuse No, DHE suites not supported
ECDH public server param reuse No
Supported Named Groups -
SSL 2 handshake compatibility Yes
0-RTT enabled No


HTTP Requests
1 https://dbda.pcf-oin.npa.go.jp/  (HTTP/1.1 200 OK)
1
Content-Type text/html; charset=utf-8
Connection close
Cache-Control no-cache
Pragma no-cache
Content-Length 247


Miscellaneous
Test date Thu, 11 Sep 2025 11:20:04 UTC
Test duration 70.898 seconds
HTTP status code 200
HTTP server signature -
Server hostname -


SSL Report v2.4.1