rufer.be
Overall grade based on: IPv4: 0 of 1 complete, 1 unreachable · IPv6: none
No HTTPS on rufer.be
Port 443 accepts connections on its IPv4 address, but no TLS handshake is completed: there is no working HTTPS.
89.31.143.90 IPv4 · Port 443 accepted the connection, but no TLS handshake was completed: the server answered with the TLS alert “unrecognized_name”.
Checked 2026-11-18 20:21 UTC
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) |
|---|---|---|
| rufer.be | 301 → https://blog.rufer.be/ → No answer (timed out) | TLS handshake failed |
| www.rufer.be | No answer (timed out) | No answer (timed out) |
- http://rufer.be redirects to HTTPS.
- www.rufer.be has no working HTTPS either (no answer).
DNS Records
As a public resolver answered for rufer.be. Looked up 2026-11-18 20:21 UTC · today
| Type | Records |
|---|---|
| A | |
| AAAA | None |
| NS | ns.udag.de ns.udag.net ns.udag.org |
| MX | 10 mx00.udag.de 20 mx01.udag.de |
| SPF | v=spf1 include:_smtp.udag.de ~all |
TLS History & Relations
Everything our scans have seen for rufer.be, first seen 2026-11-18.
Addresses
| Address | Certificate | Seen |
|---|---|---|
| 89.31.143.90 | no TLS | 2026-11-18 |
TLS history (a row per change; repeated checks only extend it)
| Since → last checked (UTC) | Grade | TLS | Certificates | Addresses |
|---|---|---|---|---|
| 2026-11-18 20:21 | No HTTPS | — | 89.31.143.90 |