ns3.automattic.com
Overall grade based on: IPv4: 1 of 1 complete · IPv6: 0 of 1 complete, 1 pending — IPv6 results are added below when their scan finishes; they do not count until then.
IPv6 scan in progress
2620:115:c00f::c000:4a05 IPv6 · Pending: IPv6 scan not started yet (it runs when the report is opened, or via POST /api/ssl-check/{domain}/ipv6).
The IPv4 report below is complete. IPv6 results will be added to this page automatically when the scan finishes.
Grade Breakdown
Protocol Support 95%
Key Exchange 90%
Cipher Strength 100%
Certificate 100%
Certificate does not match the domain name.
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) |
|---|---|---|
| ns3.automattic.com | 302 → https://en.support.wordpress.com/domain-helper/ → … → https://wordpress.com/support/domains/ → 200 OK | 302 → https://en.support.wordpress.com/domain-helper/ → … → https://wordpress.com/support/domains/ → 200 OK · certificate does not cover this name |
- http://ns3.automattic.com redirects to HTTPS.
- https://ns3.automattic.com forwards visitors to en.support.wordpress.com, a different site. View its report ›
DNS Records
As a public resolver answered for ns3.automattic.com and its domain automattic.com. Looked up 2026-11-07 22:46 UTC · 10 days ago
| Type | Records |
|---|---|
| ns3.automattic.com | |
| A | |
| AAAA | |
| MX | None |
| SPF | None |
| automattic.com | |
| A | |
| AAAA | None |
| NS | ns1.automattic.com ns2.automattic.com ns3.automattic.com ns4.automattic.com |
| MX | 10 mx-ams.automattic.com 10 mx-dfw.automattic.com |
| SPF | v=spf1 include:_spf.automattic.com include:mail.zendesk.com include:mg-spf.greenhouse.io include:sendgrid.net include:39653948.spf04.hubspotemail.net ~all |
Certificate Identity
| Common Name | ns3.automattic.com |
| Alt Names | *.wordpress.com wordpress.com |
| Issuer | CN=YR1, O=Let's Encrypt, C=US |
| Validity | 2026-11-03 to 2027-02-01 (75 days remaining) |
| Key | RSA 2048 bits (sha256RSA) |
| Serial Number | 0603C4995D4CDE726B8326C3DAF65545D279 |
| SHA256 Fingerprint | 72ad078bccfd354fbb93b180ac53d83600ee13f48854cfc3b616568c3bc14ca7 |
| Pin SHA256 | dmAkJOJRGRzesCDf0jEtV5CKDR4UTtgMrnT9F6hJ4p4= |
Certificate Properties
| Type | DV |
| Cert Transparency | Yes (SCT) |
| OCSP Must Staple | No |
| Revocation | Good (not revoked) CRL: http://yr1.c.lencr.org/122.crl No OCSP responder — revocation is published via CRL only (as CA/B Forum rules now allow). |
| DNS CAA | Yes (configured) 0 issue "letsencrypt.org" |
| Trusted By | Yes Mozilla · Apple · Android · Java · Windows |
| Name Match | No — certificate does not cover this host |
| Validity Period | 90 days (maximum 200 days for certificates issued then) |
| Policy Warnings | • Certificate does not cover ns3.automattic.com (name mismatch): browsers will show an error. |
| Chain Issues | None |
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 | No |
| 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 Secrecy | Yes (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 | 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 (server-preferred order) | |||||
| 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 (server-preferred order) | |||||
| 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 |
| TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA | 0xC013 | ECDHE | FS | 128 | Weak |
| TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA | 0xC014 | ECDHE | FS | 256 | 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_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.
Trust Chain Architecture
End-Entity Certificate
CN=wordpress.com (Issuer: CN=YR1, O=Let's Encrypt, C=US)
Intermediate CA
CN=YR1, O=Let's Encrypt, C=US (Issuer: CN=Root YR, O=ISRG, C=US)
Intermediate CA
CN=Root YR, O=ISRG, C=US (Issuer: CN=ISRG Root X1, O=Internet Security Research Group, C=US)
Root Certificate
CN=ISRG Root X1, O=Internet Security Research Group, C=US (Issuer: CN=ISRG Root X1, O=Internet Security Research Group, C=US)
TLS History & Relations
Everything our scans have seen for ns3.automattic.com, first seen 2026-11-07; current certificate since 2026-11-07.
Certificates served
| Certificate (SHA-256) | Issuer | Valid | Served |
|---|---|---|---|
| 72ad078bccfd354f… current | YR1 | 2026-11-03 → 2027-02-01 | 2026-11-07 |
Addresses
| Address | Certificate | Seen |
|---|---|---|
| 192.0.74.5 | 72ad078bccfd354f… | 2026-11-07 |
TLS history (a row per change; repeated checks only extend it)
| Since → last checked (UTC) | Grade | TLS | Certificates | Addresses |
|---|---|---|---|---|
| 2026-11-07 22:46 | T | TLS 1.3 | 72ad078bccfd354f… | 192.0.74.5 |
Other domains on the same certificate
- wordpress.com 2 names *.wordpress.com