1and1.pl
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
B 217.160.86.135 IPv4 WHOIS › B 217.160.86.136 IPv4 WHOIS › Grade Breakdown
Protocol Support 50%
Key Exchange 100%
Cipher Strength 100%
Certificate 100%
Grade capped at B: server supports obsolete TLS 1.0/1.1.
Security Vulnerabilities Detected
- •Obsolete TLS versions (1.0/1.1) supported.
- •CBC cipher suites with TLS 1.0/1.1 (BEAST, Lucky13).
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 | x25519 secp256r1 x448 secp521r1 secp384r1 (server preference order) |
| Post-Quantum Key Exchange | No (no hybrid ML-KEM group such as X25519MLKEM768) |
| HTTP/3 (QUIC) | No |
| Encrypted Client Hello | No |
| Security Features | |
| Forward Secrecy | Yes (ECDHE / DHE) |
| Downgrade Prevention | Yes (TLS_FALLBACK_SCSV) |
| 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 | Not mitigated server-side (TLS 1.0 + CBC) |
| POODLE (SSLv3) | No (SSL 3 not supported) |
| POODLE (TLS) | Possible (CBC + legacy TLS present) |
| 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 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_AES_128_CBC_SHA256 | 0xC027 | ECDHE | FS | 128 | Weak |
| TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA | 0xC013 | ECDHE | FS | 128 | Weak |
| TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384 | 0xC028 | ECDHE | FS | 256 | Weak |
| TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA | 0xC014 | ECDHE | 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_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 | TLS 1.0 | TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA | Success |
| Android 4.1.1 | TLS 1.0 | TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA | Success |
| Baidu Jan 2015 | TLS 1.0 | TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA | Success |
| Java 6 | TLS 1.0 | TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA | Success |
* 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) |
|---|---|---|
| 1and1.pl | 301 → https://ionos.eu/ → 200 OK | 301 → https://ionos.eu/ → 200 OK |
| www.1and1.pl | 403 Forbidden (unencrypted) | 403 Forbidden · certificate does not cover this name |
- http://1and1.pl redirects to HTTPS.
- https://1and1.pl forwards visitors to ionos.eu, a different site. View its report ›
- www.1and1.pl serves a certificate that does not cover its name: browsers show a security warning there.
Certificate Identity
| Common Name | 1and1.pl |
| Alt Names | ionos.eu 1and1.pl ionos.be ionos.dk ionos.nl ionos.pl ionos.pt ionos.se www.ionos.be www.ionos.dk www.ionos.eu www.ionos.nl www.ionos.pl www.ionos.pt www.ionos.se |
| Issuer | CN=Sectigo Public Server Authentication CA OV R36, O=Sectigo Limited, C=GB |
| Validity | 2026-07-17 to 2027-01-31 (75 days remaining) |
| Key | RSA 4096 bits (sha256RSA) |
| Serial Number | 00B579CBB1ECE74775954392FBD5BB6AAC |
| SHA256 Fingerprint | 29773f44fd7bdeabd95d68c3687523a9a5f4e8abc92583ba0fa6a339659a047c |
| Pin SHA256 | X37aH/2Z8mGOV4+fENSrWc3haeVEuYtZAKxwDuoxRZo= |
Certificate Properties
| Type | OV |
| Cert Transparency | Yes (SCT) |
| OCSP Must Staple | No |
| Revocation | Good (not revoked) OCSP: http://ocsp.sectigo.com CRL: http://crl.sectigo.com/SectigoPublicServerAuthenticationCAOVR36.crl |
| DNS CAA | Yes (configured) 0 issue "digicert.com" 0 issue "sectigo.com" 0 issuewild "digicert.com" 0 issuewild "sectigo.com" |
| Trusted By | Yes Mozilla · Apple · Android · Java · Windows |
| Name Match | Yes |
| Validity Period | 199 days (maximum 200 days for certificates issued then) |
| Chain Issues | • Contains anchor (root CA included in chain) |
Trust Chain Architecture
End-Entity Certificate
CN=ionos.eu, O=IONOS SE, S=Rheinland-Pfalz, C=DE (Issuer: CN=Sectigo Public Server Authentication CA OV R36, O=Sectigo Limited, C=GB)
Intermediate CA
CN=Sectigo Public Server Authentication CA OV R36, O=Sectigo Limited, C=GB (Issuer: CN=Sectigo Public Server Authentication Root R46, O=Sectigo Limited, C=GB)
Root Certificate
CN=Sectigo Public Server Authentication Root R46, O=Sectigo Limited, C=GB (Issuer: CN=Sectigo Public Server Authentication Root R46, O=Sectigo Limited, C=GB)
TLS History & Relations
Everything our scans have seen for 1and1.pl, first seen 2026-10-09; current certificate since 2026-10-24.
Certificates served
| Certificate (SHA-256) | Issuer | Valid | Served |
|---|---|---|---|
| 29773f44fd7bdeab… current | Sectigo Public Server Authentication CA OV R36 | 2026-07-17 → 2027-01-31 | 2026-10-24 |
Addresses
| Address | Certificate | Seen |
|---|---|---|
| 217.160.86.135 | 29773f44fd7bdeab… | 2026-10-24 |
| 217.160.86.136 | 29773f44fd7bdeab… | 2026-10-24 |
TLS history (a row per change; repeated checks only extend it)
| Since → last checked (UTC) | Grade | TLS | Certificates | Addresses |
|---|---|---|---|---|
| 2026-10-24 08:33 | B | TLS 1.3 | 29773f44fd7bdeab… | 217.160.86.135, 217.160.86.136 |
Other domains on the same certificate
- ionos.be 2 names
- ionos.dk 2 names
- ionos.eu 2 names
- ionos.nl 2 names
- ionos.pl 2 names
- ionos.pt 2 names
- ionos.se 2 names