SSL Check WHOIS
Dashboard / Security Report

api.tu.no

Overall grade based on: IPv4: 0 of 4 complete, 4 unreachable · IPv6: 0 of 4 complete, 4 pending — IPv6 results are added below when their scan finishes; they do not count until then.
IPv6 scan in progress
2600:9000:20b4:6a00:2:693f:b00:93a1 IPv6 · Pending: IPv6 scan not started yet (it runs when the report is opened, or via POST /api/ssl-check/{domain}/ipv6).
2600:9000:20b4:6c00:2:693f:b00:93a1 IPv6 · Pending: IPv6 scan not started yet (it runs when the report is opened, or via POST /api/ssl-check/{domain}/ipv6).
2600:9000:20b4:8c00:2:693f:b00:93a1 IPv6 · Pending: IPv6 scan not started yet (it runs when the report is opened, or via POST /api/ssl-check/{domain}/ipv6).
2600:9000:20b4:9800:2:693f:b00:93a1 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 api.tu.no

Port 443 accepts connections on all 4 IPv4 addresses, but no TLS handshake is completed: there is no working HTTPS. IPv6 is still being checked; this page updates when it finishes.

3.162.38.34 IPv4 · Port 443 accepted the connection, but no TLS handshake was completed: the server answered with the TLS alert “handshake_failure”.
3.162.38.64 IPv4 · Port 443 accepted the connection, but no TLS handshake was completed: the server answered with the TLS alert “handshake_failure”.
3.162.38.95 IPv4 · Port 443 accepted the connection, but no TLS handshake was completed: the server answered with the TLS alert “handshake_failure”.
3.162.38.96 IPv4 · Port 443 accepted the connection, but no TLS handshake was completed: the server answered with the TLS alert “handshake_failure”.
Checked 2026-11-07 13:33 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)
api.tu.no403 Forbidden (unencrypted)TLS handshake failed
  • api.tu.no is served over plain HTTP only: everything visitors send and receive is unencrypted and can be read or changed on the way.

DNS Records

As a public resolver answered for api.tu.no and its domain tu.no. Looked up 2026-11-07 13:33 UTC · 11 days ago

TypeRecords
api.tu.no
A
AAAA
MX None
SPF None
tu.no
A
AAAA None
NS
ns1.hyp.net ns2.hyp.net ns3.hyp.net
MX
0 tu-no.mail.protection.outlook.com
SPF
v=spf1 a ip4:176.58.114.74 include:_spf.tu.c.bitbit.net include:spf.protection.outlook.com include:3307297.spf06.hubspotemail.net include:sendgrid.net include:fdspfeuc.freshemail.io -all

TLS History & Relations

Everything our scans have seen for api.tu.no, first seen 2026-06-01.

Addresses

AddressCertificateSeen
3.162.38.34 no TLS 2026-11-07
3.162.38.64 no TLS 2026-11-07
3.162.38.95 no TLS 2026-11-07
3.162.38.96 no TLS 2026-11-07

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

Since → last checked (UTC)GradeTLSCertificatesAddresses
2026-11-07 13:33No HTTPS— 3.162.38.34, 3.162.38.64, 3.162.38.95, 3.162.38.96

Other hosts seen on the same addresses