SSL Check WHOIS
Dashboard / Security Report

www.huffpost.com

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+ 151.101.130.114 IPv4 WHOIS › A+ 151.101.194.114 IPv4 WHOIS › A+ 151.101.2.114 IPv4 WHOIS › A+ 151.101.66.114 IPv4 WHOIS ›
A+

Exceptional Security

Overall Rating
Assessed 2026-11-17 11:43 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 x25519 secp256r1 secp384r1 (server preference order)
Post-Quantum Key Exchange Yes 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 Yes
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_CHACHA20_POLY1305_SHA2560xCCA8ECDHEFS256Secure
TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA3840xC030ECDHEFS256Secure
TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA2560xC027ECDHEFS128Weak
TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA0xC013ECDHEFS128Weak
TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA0xC014ECDHEFS256Weak
TLS_RSA_WITH_AES_128_GCM_SHA2560x009CRSANo FS128Weak
TLS_RSA_WITH_AES_128_CBC_SHA0x002FRSANo FS128Weak
TLS_RSA_WITH_AES_256_CBC_SHA0x0035RSANo FS256Weak

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.huffpost.com301 → https://www.huffpost.com/ → 200 OK200 OK
huffpost.com301 → https://www.huffpost.com/ → 200 OK301 → https://www.huffpost.com/ → 200 OK
  • http://www.huffpost.com redirects to HTTPS.

DNS Records

As a public resolver answered for www.huffpost.com and its domain huffpost.com. Looked up 2026-11-17 11:43 UTC · today

TypeRecords
www.huffpost.com
A
AAAA None
MX None
SPF None
huffpost.com
A
AAAA None
NS
ns-1081.awsdns-07.org ns-1616.awsdns-10.co.uk ns-247.awsdns-30.com ns-843.awsdns-41.net
MX
1 aspmx.l.google.com 5 alt1.aspmx.l.google.com 5 alt2.aspmx.l.google.com 10 alt3.aspmx.l.google.com 10 alt4.aspmx.l.google.com
SPF
v=spf1 mx ip4:74.205.21.242 ip4:149.174.0.0/16 ip4:64.236.0.0/16 ip4:204.29.186.0/23 ip4:148.163.135.35/32 ip4:148.163.139.55/32 include:sendgrid.net include:_spf.google.com include:aspmx.sailthru.com include:amazonses.com -all

Certificate Identity

Common Namewww.huffpost.com
Alt Names huffpost.com *.huffpost.com *.assets.huffingtonpost.com *.assets.huffpost.com *.huffingtonpost.ca *.huffingtonpost.co.uk *.huffingtonpost.com *.huffingtonpost.com.au *.huffingtonpost.jp *.huffpost.co.uk *.elections.huffpost.com *.m.huffingtonpost.ca *.m.huffingtonpost.co.uk *.m.huffingtonpost.com.au *.m.huffingtonpost.jp *.m.huffpost.com *.m.quebec.huffingtonpost.ca *.mapi.huffpost.com *.modulous.huffpost.com *.quebec.huffingtonpost.ca *.qa.huffingtonpost.com *.staging.huffingtonpost.com *.staging.mobile.huffpost.com *.widgets.huffpost.com *.www.huffingtonpost.ca *.www.huffingtonpost.co.uk *.www.huffingtonpost.com.au *.www.huffingtonpost.jp *.www.huffpost.com *.www.quebec.huffingtonpost.ca *.login.huffpost.com *.preview.www.huffpost.com huffingtonpost.co.uk huffingtonpost.jp huffingtonpost.ca huffingtonpost.com.au
IssuerCN=GlobalSign Atlas R46 DV TLS CA 2026 Q3, O=GlobalSign nv-sa, C=BE
Validity 2026-10-11 to 2027-04-28 (162 days remaining)
KeyRSA 2048 bits (sha256RSA)
Serial Number01281B941ED21133AD28091BD308A8CF
SHA256 Fingerprint 21e556e3d8d2cf7d7034416e55c739950af51c22ded81ddc452edd383834a4b7
Pin SHA25616bDQo4fDpe9RohHwOM/a+GPixlK7UheOj/CQAXQfSU=

Certificate Properties

Type DV
Cert Transparency Yes (SCT)
OCSP Must Staple No
Revocation Good (not revoked) OCSP: http://ocsp.globalsign.com/ca/gsatlasr46dvtlsca2026q3 CRL: http://crl.globalsign.com/ca/gsatlasr46dvtlsca2026q3.crl
DNS CAA Yes (configured) 0 iodef "mailto:[email protected]" 0 issue "amazon.com" 0 issue "digicert.com" 0 issue "globalsign.com" 0 issue "letsencrypt.org"
Trusted By Yes Mozilla · Apple · Android · Java · Windows
Name Match Yes
Validity Period 199 days (maximum 200 days for certificates issued then)
Chain IssuesNone

Trust Chain Architecture

End-Entity Certificate
CN=huffpost.com (Issuer: CN=GlobalSign Atlas R46 DV TLS CA 2026 Q3, O=GlobalSign nv-sa, C=BE)
Intermediate CA
CN=GlobalSign Atlas R46 DV TLS CA 2026 Q3, O=GlobalSign nv-sa, C=BE (Issuer: CN=GlobalSign Root R46, O=GlobalSign nv-sa, C=BE)
Root Certificate
CN=GlobalSign Root R46, O=GlobalSign nv-sa, C=BE (Issuer: CN=GlobalSign Root R46, O=GlobalSign nv-sa, C=BE)

TLS History & Relations

Everything our scans have seen for www.huffpost.com, first seen 2026-06-09; current certificate since 2026-11-17.

Certificates served

Certificate (SHA-256)IssuerValidServed
21e556e3d8d2cf7d… current GlobalSign Atlas R46 DV TLS CA 2026 Q32026-10-11 → 2027-04-282026-11-17

Addresses

AddressCertificateSeen
151.101.2.114 21e556e3d8d2cf7d… 2026-11-17
151.101.66.114 21e556e3d8d2cf7d… 2026-11-17
151.101.130.114 21e556e3d8d2cf7d… 2026-11-17
151.101.194.114 21e556e3d8d2cf7d… 2026-11-17

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

Since → last checked (UTC)GradeTLSCertificatesAddresses
2026-11-17 11:43A+TLS 1.3 21e556e3d8d2cf7d… 151.101.2.114, 151.101.66.114, 151.101.130.114, 151.101.194.114

Other domains on the same certificate

Other hosts seen on the same addresses