SSL Check WHOIS
Dashboard / Security Report

norfolkdeeds.org

IPv6: no public AAAA record — the domain is reachable over IPv4 only.
A+

Exceptional Security

Overall Rating
104.17.55.64 · WHOIS ›
Assessed 2026-11-19 04:38 UTC

Grade Breakdown

Protocol Support 95%
Key Exchange 90%
Cipher Strength 100%
Certificate 100%

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)
norfolkdeeds.org301 → https://norfolkdeeds.org/ → 403 Forbidden403 Forbidden
www.norfolkdeeds.org301 → https://www.norfolkdeeds.org/ → 403 Forbidden403 Forbidden
  • http://norfolkdeeds.org redirects to HTTPS.

DNS Records

As a public resolver answered for norfolkdeeds.org. Looked up 2026-11-19 04:38 UTC · today

TypeRecords
A
AAAA None
NS
ns1dhl.name.com ns2nsy.name.com ns3cqz.name.com ns4hmp.name.com
MX
10 us-smtp-inbound-1.mimecast.com 10 us-smtp-inbound-2.mimecast.com
SPF
v=spf1 ip4:107.20.210.250 ip4:52.1.14.157 ip4:107.23.16.222 ip4:54.173.83.138 ip4:50.201.248.193 ip4:50.201.248.195 ip4:108.26.174.213 include:us._netblocks.mimecast.com include:_spf.getfused.com include:spf.protection.outlook.com include:spf.constantcontact.com a:HSYARBARRACUDA.tylertech.com a:HSDALBARRACUDA.tylertech.com -all

Certificate Identity

Common Namenorfolkdeeds.org
Alt Names norfolkdeeds.org
IssuerCN=YE1, O=Let's Encrypt, C=US
Validity 2026-09-22 to 2026-12-21 (32 days remaining)
KeyECDSA 256 bits (sha384ECDSA)
Serial Number0695C49696F92A5D32E8EA7E8255A146FC6D
SHA256 Fingerprint 11c44a04cdb3088ab79d13e7f580ec578c03a9175e5ff398e45941083ebc6cce
Pin SHA256AYxPKwXSq6Euljy4mDeLpLO68lZXbERYZxuWNs7fS78=

Certificate Properties

Type DV Domain Validated
Cert Transparency Yes (SCT)
OCSP Must Staple No
Revocation Good (not revoked) CRL: http://ye1.c.lencr.org/110.crl No OCSP responder — revocation is published via CRL only (as CA/B Forum rules now allow).
DNS CAA No (missing)
Trusted By Yes Mozilla · Apple · Android · Java · Windows
Name Match Yes
Validity Period 90 days (maximum 200 days for certificates issued then)
Chain IssuesNone

Protocol Configuration

Supported Protocols

TLS 1.3
TLS 1.2
TLS 1.1
TLS 1.0
SSL 3
SSL 2

Negotiated Cipher

TLS_AES_256_GCM_SHA384

Protocol Details

Connection
ALPN h2 http/1.1
SNI Required Yes
Supported Named Groups X25519MLKEM768 X25519Kyber768Draft00 x25519 secp256r1 secp384r1 secp521r1 (server preference order)
Post-Quantum Key Exchange Yes X25519MLKEM768, X25519Kyber768Draft00
HTTP/3 (QUIC) Yes (advertised)
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 (certificate has no OCSP responder)
HSTS Yes 180 days · includeSubDomains · preload
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 (server-preferred order)
TLS_AES_128_GCM_SHA2560x1301ECDHEFS128Secure
TLS_AES_256_GCM_SHA3840x1302ECDHEFS256Secure
TLS_CHACHA20_POLY1305_SHA2560x1303ECDHEFS256Secure
# TLS 1.2 (server-preferred order)
TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA2560xC02BECDHEFS128Secure
TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305_SHA2560xCCA9ECDHEFS256Secure
TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA3840xC02CECDHEFS256Secure
TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA2560xC023ECDHEFS128Weak
TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA3840xC024ECDHEFS256Weak

Handshake Simulation

ClientProtocolCipher SuiteResult
Chrome 120 / Win 11TLS 1.3TLS_AES_256_GCM_SHA384 Success
Chrome 80 / Win 10TLS 1.3TLS_AES_256_GCM_SHA384 Success
Firefox 115 / Win 10TLS 1.3TLS_AES_256_GCM_SHA384 Success
iOS 17 / SafariTLS 1.3TLS_CHACHA20_POLY1305_SHA256 Success
macOS 14 / SafariTLS 1.3TLS_AES_256_GCM_SHA384 Success
Android 14TLS 1.3TLS_AES_128_GCM_SHA256 Success
Chrome 69 / Win 7TLS 1.2TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 Success
Chrome 49 / XP SP3TLS 1.2TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 Success
IE 11 / Win 10TLS 1.2TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 Success
IE 11 / Win 7TLS 1.2TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 Success
Android 9.0TLS 1.2TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 Success
Android 7.0TLS 1.2TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 Success
Android 5.0TLS 1.2TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 Success
Android 4.4.2TLS 1.2TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 Success
Java 11TLS 1.2TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 Success
Java 8u121TLS 1.2TLS_ECDHE_ECDSA_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.

Trust Chain Architecture

End-Entity Certificate
CN=norfolkdeeds.org (Issuer: CN=YE1, O=Let's Encrypt, C=US)
Intermediate CA
CN=YE1, O=Let's Encrypt, C=US (Issuer: CN=Root YE, O=ISRG, C=US)
Intermediate CA
CN=Root YE, O=ISRG, C=US (Issuer: CN=ISRG Root X2, O=Internet Security Research Group, C=US)
Root Certificate
CN=ISRG Root X2, O=Internet Security Research Group, C=US (Issuer: CN=ISRG Root X2, O=Internet Security Research Group, C=US)

TLS History & Relations

Everything our scans have seen for norfolkdeeds.org, first seen 2026-11-19; current certificate since 2026-11-19.

Certificates served

Certificate (SHA-256)IssuerValidServed
11c44a04cdb3088a… current YE12026-09-22 → 2026-12-212026-11-19

Addresses

AddressCertificateSeen
104.17.55.64 11c44a04cdb3088a… 2026-11-19

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

Since → last checked (UTC)GradeTLSCertificatesAddresses
2026-11-19 04:38A+TLS 1.3 11c44a04cdb3088a… 104.17.55.64

Other hosts seen on the same addresses