SSL Check WHOIS
Dashboard / Security Report

abbott.co.jp

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+ 13.248.172.93 IPv4 WHOIS › A+ 76.223.40.250 IPv4 WHOIS ›
A+

Exceptional Security

Overall Rating
Assessed 2026-11-15 03:13 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 x25519 secp256r1 secp384r1 secp521r1 (server preference order)
Post-Quantum Key Exchange No (no hybrid ML-KEM group such as X25519MLKEM768)
HTTP/3 (QUIC) No
Encrypted Client Hello No
Security Features
Forward SecrecyYes (ECDHE / DHE)
Downgrade Prevention Yes (legacy TLS disabled)
Secure Renegotiation Supported (RFC 5746)
Extended Master Secret Yes (RFC 7627)
OCSP Stapling No
HSTS Yes 1 year · includeSubDomains
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_128_CBC_SHA2560xC027ECDHEFS128Weak
TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA3840xC030ECDHEFS256Secure
TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA3840xC028ECDHEFS256Weak

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)
abbott.co.jp301 → https://abbott.co.jp/ → … → https://www.abbott.co.jp/ → 200 OK301 → https://www.abbott.co.jp/ → 200 OK
www.abbott.co.jp301 → https://www.abbott.co.jp/ → 200 OK200 OK
  • http://abbott.co.jp redirects to HTTPS.

DNS Records

As a public resolver answered for abbott.co.jp. Looked up 2026-11-15 03:13 UTC · 2 days ago

TypeRecords
A
AAAA None
NS
rossns.abbott.com rossns2.abbott.com
MX None
SPF None

Certificate Identity

Common Nameabbott.co.jp
Alt Names abbottbrasil.com.br abbott-nutrition.com.tw abbott.co.in abbott.co.jp abbott.co.uk abbott.com.cn abbott.com.sg aus.abbott ca.abbott de.abbott es.abbott fr.abbott freestylelibre.com.sg ie.abbott kr.abbott libremedicare.com marketing.rals.com marketing.toxicology.abbott marketing2.globalpointofcare.abbott my.abbott ru.abbott timesulin.com tratandoador.abbott trylibre3.com tw.abbott vn.abbott za.abbott
IssuerCN=Sectigo Public Server Authentication CA OV R36, O=Sectigo Limited, C=GB
Validity 2026-10-06 to 2027-04-22 (156 days remaining)
KeyRSA 2048 bits (sha256RSA)
Serial Number00B74CFF7E291691FF5E480578E748B7DA
SHA256 Fingerprint a90d4d5435204f5ee33d051628313573f21639db5b5cd2f274c99403937e537b
Pin SHA256n7DTHG29zbpC8G+xqC/Bf7fSyx5dEN7CE7/mZBi+AnI=

Certificate Properties

Type OV
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=abbottbrasil.com.br, 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 abbott.co.jp, first seen 2026-11-06; current certificate since 2026-11-15.

Certificates served

Certificate (SHA-256)IssuerValidServed
a90d4d5435204f5e… current Sectigo Public Server Authentication CA OV R362026-10-06 → 2027-04-222026-11-15

Addresses

AddressCertificateSeen
13.248.172.93 a90d4d5435204f5e… 2026-11-15
76.223.40.250 a90d4d5435204f5e… 2026-11-15

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

Since → last checked (UTC)GradeTLSCertificatesAddresses
2026-11-15 03:13A+TLS 1.3 a90d4d5435204f5e… 13.248.172.93, 76.223.40.250

Other domains on the same certificate

Other hosts seen on the same addresses