SSL Check WHOIS
Dashboard / Security Report

qa.myfreestyle.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.

qa.myfreestyle.jp: SSL/TLS grade A+ (HTTPS Monitor)qa.myfreestyle.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.249.228.120 IPv4 WHOIS › A+ 13.249.228.31 IPv4 WHOIS › A+ 13.249.228.36 IPv4 WHOIS › A+ 13.249.228.41 IPv4 WHOIS ›
A+

Exceptional Security

Overall Rating
Assessed 2026-11-10 17:15 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 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)
qa.myfreestyle.jp301 → https://qa.myfreestyle.jp/ → 403 Forbidden403 Forbidden
  • http://qa.myfreestyle.jp redirects to HTTPS.

DNS Records

As a public resolver answered for qa.myfreestyle.jp and its domain myfreestyle.jp. Looked up 2026-11-10 17:15 UTC · 10 days ago

TypeRecords
qa.myfreestyle.jp
A
AAAA None
MX None
SPF None
myfreestyle.jp
A
AAAA None
NS
rossns.abbott.com rossns2.abbott.com
MX None
SPF
v=spf1 -all

Certificate Identity

Common Nameqa.myfreestyle.jp
Alt Names qa.payer.freestyle.abbott qa.adchospitaltraining.com qa.cloud.freestylelibre.de qa.cloud.whylactate.abbott qa.diabetescare.abbott qa.freestyle.abbott qa.freestylelibre.de qa.freestyleprovider.abbott qa.fsl2.freestyle.abbott qa.fsl3.freestyle.abbott qa.hellolingo.com qa.jp.abbott-diabetescare.com qa.keto.hellolingo.com qa.librerio.com qa.libresense.abbott qa.lingo.abbott.com qa.medicalaffairs.abbott qa.myfreestyle.com qa.myfreestyle.jp qa.nav.adcapps.net qa.pro.freestyle.abbott qa.provider.freestyle.abbott qa.provider.myfreestyle.com qa.sample.freestyle.abbott qa.startmyfreestyle.com qa.startmyfreestyle.freestyle.abbott qa.support.myfreestyle.com qa.trycgmsamples-provider.freestylelibre.us qa.webu.freestyle.abbott qa2.adchospitaltraining.com qa2.cloud.freestylelibre.de qa2.diabetescare.abbott qa2.freestyle.abbott qa2.freestylelibre.de qa2.freestyleprovider.abbott qa2.fsl2.freestyle.abbott qa2.fsl3.freestyle.abbott qa2.hellolingo.com qa2.jp.abbott-diabetescare.com qa2.keto.hellolingo.com qa2.librerio.com qa2.libresense.abbott qa2.lingo.abbott.com qa2.medicalaffairs.abbott qa2.myfreestyle.com qa2.nav.adcapps.net qa2.payer.freestyle.abbott qa2.pro.freestyle.abbott qa2.provider.freestyle.abbott qa2.provider.myfreestyle.com qa2.sample.freestyle.abbott qa2.startmyfreestyle.com qa2.startmyfreestyle.freestyle.abbott qa2.support.myfreestyle.com qa2.trycgmsamples-provider.freestylelibre.us qa2.webu.freestyle.abbott
IssuerCN=Sectigo Public Server Authentication CA OV R36, O=Sectigo Limited, C=GB
Validity 2026-11-03 to 2027-05-20 (181 days remaining)
KeyRSA 2048 bits (sha256RSA)
Serial Number009F2BCF7B65F2BEC7EC6388514FB0F940
SHA256 Fingerprint fc8c808bb56a46bbf336c439573d7ed2cb2448639ab2f8602677483e88000795
Pin SHA256pIWnQfRclyBjafJjEuLGq8aorvo+TQMFlNCWzg2cdjI=

Certificate Properties

Type OV Organization Validated
Cert Transparency Yes (SCT)
OCSP Must Staple No
Revocation Good (not revoked) OCSP: http://ocsp.sectigo.com CRL: http://crl.sectigo.com/SectigoPublicServerAuthenticationCAOVR36.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
• Contains anchor (root CA included in chain)

Trust Chain Architecture

End-Entity Certificate
CN=qa.payer.freestyle.abbott, O=Abbott Laboratories, S=Illinois, C=US (Issuer: CN=Sectigo Public Server Authentication CA OV R36, O=Sectigo Limited, C=GB)
Intermediate CA
CN=Sectigo Public Server Authentication CA OV R36, O=Sectigo Limited, C=GB (Issuer: CN=Sectigo Public Server Authentication Root R46, O=Sectigo Limited, C=GB)
Root Certificate
CN=Sectigo Public Server Authentication Root R46, O=Sectigo Limited, C=GB (Issuer: CN=Sectigo Public Server Authentication Root R46, O=Sectigo Limited, C=GB)

TLS History & Relations

Everything our scans have seen for qa.myfreestyle.jp, first seen 2026-11-09; current certificate since 2026-11-10.

Certificates served

Certificate (SHA-256)IssuerValidServed
fc8c808bb56a46bb… current Sectigo Public Server Authentication CA OV R362026-11-03 → 2027-05-202026-11-10

Addresses

AddressCertificateSeen
13.249.228.31 fc8c808bb56a46bb… 2026-11-10
13.249.228.36 fc8c808bb56a46bb… 2026-11-10
13.249.228.41 fc8c808bb56a46bb… 2026-11-10
13.249.228.120 fc8c808bb56a46bb… 2026-11-10

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

Since → last checked (UTC)GradeTLSCertificatesAddresses
2026-11-10 17:15A+TLS 1.3 fc8c808bb56a46bb… 13.249.228.31, 13.249.228.36, 13.249.228.41, 13.249.228.120

Other domains on the same certificate

Other hosts seen on the same addresses