getami.co
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: none
No HTTPS on getami.co
Port 443 accepts connections on its IPv4 address, but no TLS handshake is completed: there is no working HTTPS.
159.223.76.127 IPv4 · Port 443 accepted the connection, but no TLS handshake was completed: the server answered with the TLS alert “internal_error”.
Checked 2026-11-06 05:20 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) |
|---|---|---|
| getami.co | 301 → https://getami.co/ → TLS handshake failed | TLS handshake failed |
| www.getami.co | 301 → https://www.getami.co/ → TLS handshake failed | TLS handshake failed |
- http://getami.co redirects to HTTPS.
- www.getami.co has no working HTTPS either (TLS handshake failed).
DNS Records
As a public resolver answered for getami.co. Looked up 2026-11-06 05:20 UTC · 16 days ago
| Type | Records |
|---|---|
| A | |
| AAAA | None |
| NS | ns1.digitalocean.com ns2.digitalocean.com ns3.digitalocean.com |
| MX | 1 aspmx.l.google.com 5 alt1.aspmx.l.google.com 5 alt2.aspmx.l.google.com 10 alt3.aspmx.l.google.com 10 alt4.aspmx.l.google.com |
| SPF | v=spf1 include:dc-aa8e722993._spfm.getami.co ~all |
TLS History & Relations
Everything our scans have seen for getami.co, first seen 2026-11-06.
Addresses
| Address | Certificate | Seen |
|---|---|---|
| 159.223.76.127 | no TLS | 2026-11-06 |
TLS history (a row per change; repeated checks only extend it)
| Since → last checked (UTC) | Grade | TLS | Certificates | Addresses |
|---|---|---|---|---|
| 2026-11-06 05:20 | No HTTPS | — | 159.223.76.127 |