SSL Check WHOIS
Dashboard / Security Report

bnfw.co.jp

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+ 52.222.169.104 IPv4 WHOIS › A+ 52.222.169.129 IPv4 WHOIS › A+ 52.222.169.36 IPv4 WHOIS › A+ 52.222.169.44 IPv4 WHOIS ›
A+

Exceptional Security

Overall Rating
Assessed 2026-11-01 17:41 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 No
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 1 year
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)
bnfw.co.jp301 → https://bnfw.co.jp/ → … → https://www.bnfw.co.jp/ → 200 OK301 → https://www.bnfw.co.jp/ → 200 OK
www.bnfw.co.jp301 → https://www.bnfw.co.jp/ → 200 OK200 OK
  • http://bnfw.co.jp redirects to HTTPS.

Certificate Identity

Common Namebnfw.co.jp
Alt Names bnfw.co.jp *.bnfw.co.jp
IssuerCN=Amazon RSA 2048 M01, O=Amazon, C=US
Validity 2026-08-27 to 2027-03-12 (115 days remaining)
KeyRSA 2048 bits (sha256RSA)
Serial Number079B71F1E0A823892E38A4581B0C4EF9
SHA256 Fingerprint 94fc75a6d5c4e112542bb5975419f365d5acddd09d5442f30dcea65bdc378775
Pin SHA256N163LXcJo5LVM7bKEy5diZhXcgeSdXr8ZFPVsFA34bU=

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=bnfw.co.jp (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 bnfw.co.jp, first seen 2026-11-01; current certificate since 2026-11-01.

Certificates served

Certificate (SHA-256)IssuerValidServed
94fc75a6d5c4e112… current Amazon RSA 2048 M012026-08-27 → 2027-03-122026-11-01

Addresses

AddressCertificateSeen
52.222.169.36 94fc75a6d5c4e112… 2026-11-01
52.222.169.44 94fc75a6d5c4e112… 2026-11-01
52.222.169.104 94fc75a6d5c4e112… 2026-11-01
52.222.169.129 94fc75a6d5c4e112… 2026-11-01

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

Since → last checked (UTC)GradeTLSCertificatesAddresses
2026-11-01 17:41A+TLS 1.3 94fc75a6d5c4e112… 52.222.169.36, 52.222.169.44, 52.222.169.104, 52.222.169.129

Other hosts seen on the same addresses