huffpost.co.uk
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.227.231.11 IPv4 WHOIS › A+ 13.227.231.12 IPv4 WHOIS › A+ 13.227.231.47 IPv4 WHOIS › A+ 13.227.231.5 IPv4 WHOIS › 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 Secrecy | Yes (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 | Unknown (the HTTPS request to this IP failed) |
| 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 Compression | No (not supported by .NET TLS stack) |
| Heartbleed | Not tested |
Cipher Suite Analysis
| Cipher Suite | Hex | Key Exchange | FS | Bits | Strength |
|---|---|---|---|---|---|
| # TLS 1.3 | |||||
| TLS_AES_128_GCM_SHA256 | 0x1301 | ECDHE | FS | 128 | Secure |
| TLS_AES_256_GCM_SHA384 | 0x1302 | ECDHE | FS | 256 | Secure |
| TLS_CHACHA20_POLY1305_SHA256 | 0x1303 | ECDHE | FS | 256 | Secure |
| # TLS 1.2 | |||||
| TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 | 0xC02F | ECDHE | FS | 128 | Secure |
| TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 | 0xC030 | ECDHE | FS | 256 | Secure |
| TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256 | 0xCCA8 | ECDHE | FS | 256 | Secure |
Handshake Simulation
| Client | Protocol | Cipher Suite | Result |
|---|---|---|---|
| Chrome 120 / Win 11 | TLS 1.3 | TLS_AES_256_GCM_SHA384 | Success |
| Chrome 80 / Win 10 | TLS 1.3 | TLS_AES_256_GCM_SHA384 | Success |
| Firefox 115 / Win 10 | TLS 1.3 | TLS_AES_256_GCM_SHA384 | Success |
| iOS 17 / Safari | TLS 1.3 | TLS_CHACHA20_POLY1305_SHA256 | Success |
| macOS 14 / Safari | TLS 1.3 | TLS_AES_256_GCM_SHA384 | Success |
| Android 14 | TLS 1.3 | TLS_AES_128_GCM_SHA256 | Success |
| Chrome 69 / Win 7 | TLS 1.2 | TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 | Success |
| Chrome 49 / XP SP3 | TLS 1.2 | TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 | Success |
| IE 11 / Win 10 | TLS 1.2 | TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 | Success |
| IE 11 / Win 7 | TLS 1.2 | TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 | Success |
| Android 9.0 | TLS 1.2 | TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 | Success |
| Android 7.0 | TLS 1.2 | TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 | Success |
| Android 5.0 | TLS 1.2 | TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 | Success |
| Android 4.4.2 | TLS 1.2 | TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 | Success |
| Java 11 | TLS 1.2 | TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 | Success |
| Java 8u121 | TLS 1.2 | TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 | Success |
| 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.
| Host | http:// (port 80) | https:// (port 443) |
|---|---|---|
| huffpost.co.uk | 301 → https://huffpost.co.uk/ → … → https://www.huffingtonpost.co.uk/ → 200 OK | 301 → https://www.huffingtonpost.co.uk/ → 200 OK |
| www.huffpost.co.uk | 301 → https://www.huffpost.co.uk/ → … → https://www.huffingtonpost.co.uk/ → 200 OK | 301 → https://www.huffingtonpost.co.uk/ → 200 OK |
- http://huffpost.co.uk redirects to HTTPS.
- https://huffpost.co.uk forwards visitors to www.huffingtonpost.co.uk, a different site. View its report ›
DNS Records
As a public resolver answered for huffpost.co.uk. Looked up 2026-11-17 12:04 UTC · today
| Type | Records |
|---|---|
| A | |
| AAAA | None |
| NS | ns-1070.awsdns-05.org ns-1644.awsdns-13.co.uk ns-189.awsdns-23.com ns-940.awsdns-53.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 include:_spf.google.com ~all |
Certificate Identity
| Common Name | huffpost.co.uk |
| Alt Names | huffpost.co.uk thespoils.huffpost.co.uk staging.contributor.huffpost.co.uk search.huffpost.co.uk contributor.huffpost.co.uk www.huffpost.co.uk |
| Issuer | CN=Amazon RSA 2048 M04, O=Amazon, C=US |
| Validity | 2026-07-24 to 2027-02-06 (81 days remaining) |
| Key | RSA 2048 bits (sha256RSA) |
| Serial Number | 02BBDC7537FF21C2DA69F46E8B06423D |
| SHA256 Fingerprint | 2f0136632350f1d36c8c1de5276b702aeee1dc3f69e3c7c7c0e653f3e01d9f19 |
| Pin SHA256 | tHIbL3Wx6gpqkgFaZgG3kEkkKqo/ityz5uAqSvVmNoo= |
Certificate Properties
| Type | DV |
| 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 | 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 | 198 days (maximum 200 days for certificates issued then) |
| Chain Issues | None |
Trust Chain Architecture
End-Entity Certificate
CN=huffpost.co.uk (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 huffpost.co.uk, first seen 2026-06-09; current certificate since 2026-11-17.
Certificates served
| Certificate (SHA-256) | Issuer | Valid | Served |
|---|---|---|---|
| 2f0136632350f1d3… current | Amazon RSA 2048 M04 | 2026-07-24 → 2027-02-06 | 2026-11-17 |
Addresses
| Address | Certificate | Seen |
|---|---|---|
| 13.227.231.5 | 2f0136632350f1d3… | 2026-11-17 |
| 13.227.231.11 | 2f0136632350f1d3… | 2026-11-17 |
| 13.227.231.12 | 2f0136632350f1d3… | 2026-11-17 |
| 13.227.231.47 | 2f0136632350f1d3… | 2026-11-17 |
TLS history (a row per change; repeated checks only extend it)
| Since → last checked (UTC) | Grade | TLS | Certificates | Addresses |
|---|---|---|---|---|
| 2026-11-17 12:04 | A+ | TLS 1.3 | 2f0136632350f1d3… | 13.227.231.5, 13.227.231.11, 13.227.231.12, 13.227.231.47 |
Other hosts seen on the same addresses
aaml.org accounts-us-prod.jaguarmexico.com.mx accounts-us-prod.landrover.ca accounts-us-prod.landrover.com.mx agenda.znanylekarz.pl animaapp.com api.widgets.znanylekarz.pl arizent.arizent.production.k2.m1.brightspot.cloud belezanaweb.com.br buildasign.com career.io cspan.org cspanstore.com c-spanstore.org designcrowd.com.au designcrowd.co.uk designcrowd.fr dnsbelgium.brussels dnsbelgium.de dnsbelgium.net dnsbelgium.org dns.brussels dnsbrussels.be dns.vlaanderen dodoapp.co edgenuity.com exporo.de flamingflamingos.be fuel.tv gafasworld.com.co