bumping.app
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.
Overall grade based on: IPv4: 0 of 1 complete, 1 unreachable · 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
2607:f1c0:100f:f000::2b2 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.
No HTTPS over IPv4 on bumping.app
Port 443 accepts connections on its IPv4 address, but no TLS handshake is completed: there is no working HTTPS. IPv6 is still being checked; this page updates when it finishes.
74.208.236.133 IPv4 · Port 443 accepted the connection, but no TLS handshake was completed: the server answered with the TLS alert “internal_error”.
Checked 2026-10-24 14:09 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) |
|---|---|---|
| bumping.app | 403 Forbidden (unencrypted) | TLS handshake failed |
| www.bumping.app | 403 Forbidden (unencrypted) | TLS handshake failed |
- bumping.app is served over plain HTTP only: everything visitors send and receive is unencrypted and can be read or changed on the way.
- www.bumping.app has no working HTTPS either (TLS handshake failed).
TLS History & Relations
Everything our scans have seen for bumping.app, first seen 2026-10-24.
Addresses
| Address | Certificate | Seen |
|---|---|---|
| 74.208.236.133 | no TLS | 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 14:09 | No HTTPS | — | 74.208.236.133 |