SSL Check WHOIS
Dashboard / Security Report

agoogleaday.com

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
2a00:1450:400c:c09::79 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 agoogleaday.com

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.

64.233.166.121 IPv4 · Port 443 accepted the connection, but no TLS handshake was completed: the server closed the connection.
Checked 2026-11-17 14:34 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.

Hosthttp:// (port 80)https:// (port 443)
agoogleaday.com301 → http://www.agoogleaday.com/ → 200 OKTLS handshake failed
www.agoogleaday.com200 OK (unencrypted)TLS handshake failed
  • http://agoogleaday.com redirects to http://www.agoogleaday.com/, which is not HTTPS either.
  • www.agoogleaday.com has no working HTTPS either (TLS handshake failed).

DNS Records

As a public resolver answered for agoogleaday.com. Looked up 2026-11-17 14:34 UTC · today

TypeRecords
A
AAAA
NS
ns1.agoogleaday.com ns2.agoogleaday.com ns3.agoogleaday.com ns4.agoogleaday.com
MX None
SPF
v=spf1 ?all

TLS History & Relations

Everything our scans have seen for agoogleaday.com, first seen 2026-11-17.

Addresses

AddressCertificateSeen
64.233.166.121 no TLS 2026-11-17

TLS history (a row per change; repeated checks only extend it)

Since → last checked (UTC)GradeTLSCertificatesAddresses
2026-11-17 14:34No HTTPS— 64.233.166.121

Other hosts seen on the same addresses