heartland.edu
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.
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+ 20.118.40.53 IPv4 WHOIS › A+ 20.118.56.11 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_256_GCM_SHA384
Protocol Details
| Connection | |
| ALPN | http/1.1 |
| SNI Required | Yes |
| Supported Named Groups | X25519MLKEM768 secp521r1 secp384r1 secp256r1 (server preference order) |
| Post-Quantum Key Exchange | Yes X25519MLKEM768 |
| HTTP/3 (QUIC) | No |
| Encrypted Client Hello | No |
| Security Features | |
| Forward Secrecy | Yes (ECDHE / DHE) |
| Downgrade Prevention | Yes (legacy TLS disabled) |
| Secure Renegotiation | Supported (RFC 5746) |
| Extended Master Secret | Yes (RFC 7627) |
| OCSP Stapling | Yes |
| HSTS | No |
| 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_256_GCM_SHA384 | 0x1302 | ECDHE | FS | 256 | Secure |
| TLS_AES_128_GCM_SHA256 | 0x1301 | ECDHE | FS | 128 | Secure |
| # TLS 1.2 | |||||
| TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 | 0xC030 | ECDHE | FS | 256 | Secure |
| TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 | 0xC02F | ECDHE | FS | 128 | Secure |
| TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384 | 0xC028 | ECDHE | FS | 256 | Weak |
| TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256 | 0xC027 | ECDHE | FS | 128 | Weak |
| TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA | 0xC014 | ECDHE | FS | 256 | Weak |
| TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA | 0xC013 | ECDHE | FS | 128 | Weak |
| TLS_RSA_WITH_AES_256_GCM_SHA384 | 0x009D | RSA | No FS | 256 | Weak |
| TLS_RSA_WITH_AES_128_GCM_SHA256 | 0x009C | RSA | No FS | 128 | Weak |
| TLS_RSA_WITH_AES_256_CBC_SHA256 | 0x003D | RSA | No FS | 256 | Weak |
| TLS_RSA_WITH_AES_128_CBC_SHA256 | 0x003C | RSA | No FS | 128 | Weak |
| TLS_RSA_WITH_AES_256_CBC_SHA | 0x0035 | RSA | No FS | 256 | Weak |
| TLS_RSA_WITH_AES_128_CBC_SHA | 0x002F | RSA | No FS | 128 | Weak |
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_AES_256_GCM_SHA384 | 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_256_GCM_SHA384 | Success |
| Chrome 49 / XP SP3 | TLS 1.2 | TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 | Success |
| IE 11 / Win 10 | TLS 1.2 | TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 | Success |
| IE 11 / Win 7 | TLS 1.2 | TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 | Success |
| Android 9.0 | TLS 1.2 | TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 | Success |
| Android 7.0 | TLS 1.2 | TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 | Success |
| Android 5.0 | TLS 1.2 | TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 | Success |
| Android 4.4.2 | TLS 1.2 | TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 | Success |
| Java 11 | TLS 1.2 | TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 | Success |
| Java 8u121 | TLS 1.2 | TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 | 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) |
|---|---|---|
| heartland.edu | 301 → https://heartland.edu/ → … → https://www.heartland.edu/ → 200 OK | 301 → https://www.heartland.edu/ → 200 OK |
| www.heartland.edu | 301 → https://www.heartland.edu/ → 200 OK | 200 OK |
- http://heartland.edu redirects to HTTPS.
DNS Records
As a public resolver answered for heartland.edu. Looked up 2026-11-10 14:04 UTC · 10 days ago
| Type | Records |
|---|---|
| A | |
| AAAA | None |
| NS | ns1.heartland.edu ns1.illinois.net ns2.heartland.edu ns2.illinois.net |
| MX | 10 us-smtp-inbound-1.mimecast.com 10 us-smtp-inbound-2.mimecast.com |
| SPF | v=spf1 ip4:216.125.243.162 ip4:216.125.243.163 ip4:216.124.52.100 ip4:216.124.52.102 ip4:216.124.56.100 ip4:216.124.56.102 ip4:205.139.105.140 ip4:198.21.1.32 ip4:159.183.172.108 ip4:159.183.172.154 ip4:159.183.172.159 ip4:159.183.172.168 ip4:159.183.172.173 ip4:208.117.49.214 ip4:52.210.155.131 ip4:34.194.230.233 ip4:34.230.107.215 ip4:34.250.203.24 ip4:34.250.117.27 ip4:52.62.198.211 ip4:52.60.116.9 ip4:52.60.157.49 ip4:150.230.240.226 ip4:52.70.104.58 ip4:35.174.117.211 ip4:51.112.32.123 ip4:3.28.77.232 ip4:52.86.177.169 ip4:168.245.29.173 ip4:139.60.0.0/24 ip4:139.60.1.0/24 ip4:139.60.2.0/24 ip4:139.60.3.0/24 ip4:64.74.237.230/31 ip4:216.147.212.20/30 include:us._netblocks.mimecast.com include:spf.protection.outlook.com include:_spf.regroup.com include:_spf.salesforce.com ~all |
Certificate Identity
| Common Name | heartland.edu |
| Alt Names | heartland.edu |
| Issuer | CN=GeoTrust TLS RSA CA G1, OU=www.digicert.com, O=DigiCert Inc, C=US |
| Validity | 2026-09-23 to 2027-03-23 (123 days remaining) |
| Key | RSA 2048 bits (sha256RSA) |
| Serial Number | 0A99F51011B40C4F8471C0F408453FF7 |
| SHA256 Fingerprint | a5b76aba97661f4cc78ae88b2def055aece34df741b1906aa3a96edc7f3ee3ac |
| Pin SHA256 | CRk4EHGvj0KelPKPDzz4jxe4pQXJCzDPLSvlivHXguU= |
Certificate Properties
| Type | DV Domain Validated |
| Cert Transparency | Yes (SCT) |
| OCSP Must Staple | No |
| Revocation | Good (not revoked) OCSP: http://status.geotrust.com CRL: http://cdp.geotrust.com/GeoTrustTLSRSACAG1.crl |
| DNS CAA | No (missing) |
| Trusted By | Yes Mozilla · Apple · Android · Java · Windows |
| Name Match | Yes |
| Validity Period | 182 days (maximum 200 days for certificates issued then) |
| Chain Issues | None |
Trust Chain Architecture
End-Entity Certificate
CN=heartland.edu (Issuer: CN=GeoTrust TLS RSA CA G1, OU=www.digicert.com, O=DigiCert Inc, C=US)
Intermediate CA
CN=GeoTrust TLS RSA CA G1, OU=www.digicert.com, O=DigiCert Inc, C=US (Issuer: CN=DigiCert Global Root G2, OU=www.digicert.com, O=DigiCert Inc, C=US)
Root Certificate
CN=DigiCert Global Root G2, OU=www.digicert.com, O=DigiCert Inc, C=US (Issuer: CN=DigiCert Global Root G2, OU=www.digicert.com, O=DigiCert Inc, C=US)
TLS History & Relations
Everything our scans have seen for heartland.edu, first seen 2026-11-10; current certificate since 2026-11-10.
Certificates served
| Certificate (SHA-256) | Issuer | Valid | Served |
|---|---|---|---|
| a5b76aba97661f4c… current | GeoTrust TLS RSA CA G1 | 2026-09-23 → 2027-03-23 | 2026-11-10 |
Addresses
| Address | Certificate | Seen |
|---|---|---|
| 20.118.40.53 | a5b76aba97661f4c… | 2026-11-10 |
| 20.118.56.11 | a5b76aba97661f4c… | 2026-11-10 |
TLS history (a row per change; repeated checks only extend it)
| Since → last checked (UTC) | Grade | TLS | Certificates | Addresses |
|---|---|---|---|---|
| 2026-11-10 14:04 | A+ | TLS 1.3 | a5b76aba97661f4c… | 20.118.40.53, 20.118.56.11 |