SSL Check WHOIS
objc.io has no HTTPS: Port 443 refuses connections on its IPv4 address: no HTTPS server is running. The site is served on www.objc.io; this is its report. (objc.io checked 2026-10-23 00:24 UTC)
Dashboard / Security Report

www.objc.io

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.

www.objc.io: SSL/TLS grade B (HTTPS Monitor)www.objc.ioB
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
B 13.249.228.112 IPv4 WHOIS › B 13.249.228.28 IPv4 WHOIS › B 13.249.228.55 IPv4 WHOIS › B 13.249.228.98 IPv4 WHOIS ›
B

Adequate Protection

Overall Rating
Assessed 2026-11-18 23:45 UTC

Grade Breakdown

Protocol Support 70%
Key Exchange 90%
Cipher Strength 100%
Certificate 100%
Grade capped at B: server supports obsolete TLS 1.0/1.1.

Security Vulnerabilities Detected

  • •Obsolete TLS versions (1.0/1.1) supported.
  • •CBC cipher suites with TLS 1.0/1.1 (BEAST, Lucky13).

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, TLS_FALLBACK_SCSV — shown as unknown, not as unsupported
Downgrade Prevention Unknown
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) Possible (CBC + legacy TLS present)
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_128_CBC_SHA0xC013ECDHEFS128Weak
TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA3840xC030ECDHEFS256Secure
TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA2560xCCA8ECDHEFS256Secure
TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA3840xC028ECDHEFS256Weak
TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA0xC014ECDHEFS256Weak
TLS_RSA_WITH_AES_128_GCM_SHA2560x009CRSANo FS128Weak
TLS_RSA_WITH_AES_256_GCM_SHA3840x009DRSANo FS256Weak
TLS_RSA_WITH_AES_128_CBC_SHA2560x003CRSANo FS128Weak
TLS_RSA_WITH_AES_256_CBC_SHA0x0035RSANo FS256Weak
TLS_RSA_WITH_AES_128_CBC_SHA0x002FRSANo FS128Weak

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)
www.objc.io301 → https://www.objc.io/ → 200 OK200 OK
objc.io301 → http://www.objc.io/ → … → https://www.objc.io/ → 200 OKConnection refused
  • http://www.objc.io redirects to HTTPS.
  • objc.io has no working HTTPS (connection refused): visitors who type that name do not reach the HTTPS site.

DNS Records

As a public resolver answered for www.objc.io and its domain objc.io. Looked up 2026-11-18 23:45 UTC · 1 day ago

TypeRecords
www.objc.io
A
AAAA None
MX None
SPF None
objc.io
A
AAAA None
NS
ns-121-a.gandi.net ns-251-c.gandi.net ns-36-b.gandi.net
MX
1 aspmx.l.google.com 5 alt1.aspmx.l.google.com 5 alt2.aspmx.l.google.com 10 aspmx2.googlemail.com 10 aspmx3.googlemail.com
SPF
v=spf1 include:_spf.google.com ~all

Certificate Identity

Common Namewww.objc.io
Alt Names objc.io www.objc.io
IssuerCN=Amazon RSA 2048 M04, O=Amazon, C=US
Validity 2026-08-05 to 2027-02-18 (90 days remaining)
KeyRSA 2048 bits (sha256RSA)
Serial Number017FBA1FDB2CFD8347482664109ED282
SHA256 Fingerprint a371485733d118e09f0bf598c663a31cd8e2e7402dff1a47ef22b6069d1e7c1e
Pin SHA256O/Jt5mIwZ4zaSa1PcGrLPNVMtB750s0mqJHL7ZvKAMk=

Certificate Properties

Type DV Domain Validated
Cert Transparency Yes (SCT)
OCSP Must Staple No
Revocation Good (not revoked) OCSP: http://ocsp.r2m04.amazontrust.com CRL: http://crl.r2m04.amazontrust.com/r2m04.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=objc.io (Issuer: CN=Amazon RSA 2048 M04, O=Amazon, C=US)
Intermediate CA
CN=Amazon RSA 2048 M04, 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 www.objc.io, first seen 2026-11-18; current certificate since 2026-11-18.

Certificates served

Certificate (SHA-256)IssuerValidServed
a371485733d118e0… current Amazon RSA 2048 M042026-08-05 → 2027-02-182026-11-18

Addresses

AddressCertificateSeen
13.249.228.28 a371485733d118e0… 2026-11-18
13.249.228.55 a371485733d118e0… 2026-11-18
13.249.228.98 a371485733d118e0… 2026-11-18
13.249.228.112 a371485733d118e0… 2026-11-18

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

Since → last checked (UTC)GradeTLSCertificatesAddresses
2026-11-18 23:45BTLS 1.3 a371485733d118e0… 13.249.228.28, 13.249.228.55, 13.249.228.98, 13.249.228.112

Other hosts seen on the same addresses