api.123-reg.co.uk
Overall grade based on: IPv4: 2 of 2 complete · IPv6: 0 of 2 complete, 2 pending — IPv6 results are added below when their scan finishes; they do not count until then.
IPv6 scan in progress
2a02:26f0:2b80:2f::215:8f45 IPv6 · Pending: IPv6 scan not started yet (it runs when the report is opened, or via POST /api/ssl-check/{domain}/ipv6).
2a02:26f0:2b80:2f::215:8f4c 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.
All 2 endpoints share identical configuration Select an IP for owner, ASN & location
A+ 2.21.23.230 IPv4 WHOIS › A+ 2.21.23.251 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 x25519 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_CHACHA20_POLY1305_SHA256 | 0x1303 | ECDHE | FS | 256 | Secure |
| TLS_AES_128_GCM_SHA256 | 0x1301 | ECDHE | FS | 128 | Secure |
| TLS_AES_128_CCM_SHA256 | 0x1304 | 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_CHACHA20_POLY1305_SHA256 | 0xCCA8 | ECDHE | FS | 256 | 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 |
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_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) |
|---|---|---|
| api.123-reg.co.uk | 404 Not Found (unencrypted) | 404 Not Found |
- http://api.123-reg.co.uk answers without redirecting to HTTPS: visitors who type the address without https:// get an unencrypted page.
DNS Records
As a public resolver answered for api.123-reg.co.uk and its domain 123-reg.co.uk. Looked up 2026-11-12 04:08 UTC · 5 days ago
| Type | Records |
|---|---|
| api.123-reg.co.uk | |
| A | |
| AAAA | |
| MX | None |
| SPF | None |
| 123-reg.co.uk | |
| A | |
| AAAA | |
| NS | a1-245.akam.net a11-64.akam.net a20-65.akam.net a6-66.akam.net a8-67.akam.net a9-67.akam.net |
| MX | 5 mx0.hosteurope.de |
| SPF | v=spf1 ip4:109.68.39.0/24 ip4:80.237.138.26 ip4:92.51.170.64/27 ip4:68.178.213.0/24 ip4:80.90.192.0/24 ip4:94.136.42.40/29 ip4:94.136.40.128/29 ip4:94.136.40.29 ip4:92.60.112.0/24 ip6:2a02:4e8:4:2099::40:1/64 ip6:2a02:4e8:1:2::/64 ip4:109.68.33.0/24 include:trustpilotservice.com include:sendgrid.net include:mailcontrol.com include:spf-0.secureserver.net include:sparkpostmail.com include:spf.em.secureserver.net -all |
Certificate Identity
Certificate Properties
| Type | DV |
| Cert Transparency | Yes (SCT) |
| OCSP Must Staple | No |
| Revocation | Good (not revoked) OCSP: http://ocsp.godaddy.com/ CRL: http://crl.godaddy.com/gdr1v1dv_s1-19.crl |
| DNS CAA | Yes (configured) 0 issue "letsencrypt.org;accounturi=https://acme-v02.api.letsencrypt.org/acme/acct/445632" 0 issue "globalsign.com" 0 issue "godaddy.com" |
| Trusted By | Yes Mozilla · Apple · Android · Java · Windows |
| Name Match | Yes |
| Validity Period | 198 days (maximum 200 days for certificates issued then) |
| Chain Issues | • Contains anchor (root CA included in chain) |
Trust Chain Architecture
End-Entity Certificate
CN=www.123-reg.co.uk (Issuer: CN=GoDaddy TLS Intermediate CA DV - R1v1, O=GoDaddy.com, C=US)
Intermediate CA
CN=GoDaddy TLS Intermediate CA DV - R1v1, O=GoDaddy.com, C=US (Issuer: CN=GoDaddy TLS Root CA - R1, O=GoDaddy.com, C=US)
Intermediate CA
CN=GoDaddy TLS Root CA - R1, O=GoDaddy.com, C=US (Issuer: CN=Go Daddy Root Certificate Authority - G2, O="GoDaddy.com, Inc.", L=Scottsdale, S=Arizona, C=US)
Root Certificate
CN=Go Daddy Root Certificate Authority - G2, O="GoDaddy.com, Inc.", L=Scottsdale, S=Arizona, C=US (Issuer: CN=Go Daddy Root Certificate Authority - G2, O="GoDaddy.com, Inc.", L=Scottsdale, S=Arizona, C=US)
TLS History & Relations
Everything our scans have seen for api.123-reg.co.uk, first seen 2026-10-09; current certificate since 2026-11-12.
Certificates served
| Certificate (SHA-256) | Issuer | Valid | Served |
|---|---|---|---|
| 1d51b3486e20294a… current | GoDaddy TLS Intermediate CA DV - R1v1 | 2026-11-10 → 2027-05-27 | 2026-11-12 |
Addresses
| Address | Certificate | Seen |
|---|---|---|
| 2.21.23.230 | 1d51b3486e20294a… | 2026-11-12 |
| 2.21.23.251 | 1d51b3486e20294a… | 2026-11-12 |
TLS history (a row per change; repeated checks only extend it)
| Since → last checked (UTC) | Grade | TLS | Certificates | Addresses |
|---|---|---|---|---|
| 2026-11-12 04:08 | A+ | TLS 1.3 | 1d51b3486e20294a… | 2.21.23.230, 2.21.23.251 |