SSL Check WHOIS
Dashboard / Security Report

mon.ruter.no

IPv6: no public AAAA record — the domain is reachable over IPv4 only.
All 4 endpoints share identical configuration Select an IP for owner, ASN & location
A+ 13.227.173.19 IPv4 WHOIS › A+ 13.227.173.49 IPv4 WHOIS › A+ 13.227.173.83 IPv4 WHOIS › A+ 13.227.173.99 IPv4 WHOIS ›
A+

Exceptional Security

Overall Rating
Assessed 2026-11-07 02:50 UTC

Grade Breakdown

Protocol Support 95%
Key Exchange 90%
Cipher Strength 100%
Certificate 100%

Protocol Configuration

Supported Protocols

TLS 1.3
TLS 1.2
TLS 1.1
TLS 1.0
SSL 3
SSL 2

Negotiated Cipher

TLS_AES_128_GCM_SHA256

Protocol Details

Connection
ALPN h2 http/1.1
SNI Required Yes
Supported Named Groups X25519MLKEM768 SecP256r1MLKEM768 x25519 secp256r1 secp384r1 (server preference order)
Post-Quantum Key Exchange Yes X25519MLKEM768, SecP256r1MLKEM768
HTTP/3 (QUIC) Yes (advertised)
Encrypted Client Hello No
Security Features
Forward SecrecyYes (ECDHE / DHE)
Scan Coverage Incomplete no answer in time for: key exchange groups — shown as unknown, not as unsupported
Downgrade Prevention Yes (legacy TLS disabled)
Secure Renegotiation Supported (RFC 5746)
Extended Master Secret Yes (RFC 7627)
OCSP Stapling No
HSTS No
HSTS Preloading N/A (HSTS not enabled)
Security Checks
BEAST attack Mitigated
POODLE (SSLv3) No (SSL 3 not supported)
POODLE (TLS) No
RC4 No
SSL/TLS CompressionNo (not supported by .NET TLS stack)
HeartbleedNot tested

Cipher Suite Analysis

Cipher SuiteHexKey ExchangeFSBitsStrength
# TLS 1.3
TLS_AES_128_GCM_SHA2560x1301ECDHEFS128Secure
TLS_AES_256_GCM_SHA3840x1302ECDHEFS256Secure
TLS_CHACHA20_POLY1305_SHA2560x1303ECDHEFS256Secure
# TLS 1.2
TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA2560xC02FECDHEFS128Secure
TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA3840xC030ECDHEFS256Secure
TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA2560xCCA8ECDHEFS256Secure

Handshake Simulation

ClientProtocolCipher SuiteResult
Chrome 120 / Win 11TLS 1.3TLS_AES_256_GCM_SHA384Success
Chrome 80 / Win 10TLS 1.3TLS_AES_256_GCM_SHA384Success
Firefox 115 / Win 10TLS 1.3TLS_AES_256_GCM_SHA384Success
iOS 17 / SafariTLS 1.3TLS_CHACHA20_POLY1305_SHA256Success
macOS 14 / SafariTLS 1.3TLS_AES_256_GCM_SHA384Success
Android 14TLS 1.3TLS_AES_128_GCM_SHA256Success
Chrome 69 / Win 7TLS 1.2TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256Success
Chrome 49 / XP SP3TLS 1.2TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256Success
IE 11 / Win 10TLS 1.2TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256Success
IE 11 / Win 7TLS 1.2TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256Success
Android 9.0TLS 1.2TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256Success
Android 7.0TLS 1.2TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256Success
Android 5.0TLS 1.2TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256Success
Android 4.4.2TLS 1.2TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256Success
Java 11TLS 1.2TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256Success
Java 8u121TLS 1.2TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256Success
Android 4.0.4--No
Android 4.1.1--No
Baidu Jan 2015--No
Java 6--No

* Simulated based on server's supported protocols and cipher configuration.

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)
mon.ruter.no301 → https://mon.ruter.no/ → 200 OK200 OK
  • http://mon.ruter.no redirects to HTTPS.

DNS Records

As a public resolver answered for mon.ruter.no and its domain ruter.no. Looked up 2026-11-07 02:50 UTC · 10 days ago

TypeRecords
mon.ruter.no
A
AAAA None
MX None
SPF None
ruter.no
A
AAAA None
NS
suzanne.ns.cloudflare.com zeus.ns.cloudflare.com
MX
10 ruter-no.mail.protection.outlook.com
SPF
v=spf1 include:_spf.intility.no mx include:sendgrid.net mx include:_spf.sndr.no ip4:195.225.27.32 ip4:185.38.121.22 include:spf.protection.outlook.com include:_spf.eu.mailgun.org include:spf.eu.exclaimer.net include:amazonses.com ~all

Certificate Identity

Common Namemon.ruter.no
Alt Names ruter.redirect.tetapps.com applink.ruter.no driver.skoleskyss.no dagsplan.tet.digital dagsplan.ruter.no mon.ruter.no rutergpt.ruter.no tt.ruter.no minside.ruter.no web-proxy.ruter.no app.skoleskyss.no bestillingadmin.ruter.no app.ruter.no reise.ruter.no
IssuerCN=Amazon RSA 2048 M04, O=Amazon, C=US
Validity 2026-11-04 to 2027-05-20 (184 days remaining)
KeyRSA 2048 bits (sha256RSA)
Serial Number01C75E9232405C9AAF6BE6D850652936
SHA256 Fingerprint e350fc17e303dc88a5b1a44cbc6043fbc39879c4b3a027774ff72d296430d64a
Pin SHA256BSMYSVa9RPZaqXzJaucjHZtor6wspOEc/jzzxosq8Uk=

Certificate Properties

Type DV
Cert Transparency Yes (SCT)
OCSP Must Staple No
Revocation Good (not revoked) OCSP: http://ocsp.r2m04.amazontrust.com CRL: http://crl.r2m04.amazontrust.com/r2m04.crl
DNS CAA No (missing)
Trusted By Yes Mozilla · Apple · Android · Java · Windows
Name Match Yes
Validity Period 198 days (maximum 200 days for certificates issued then)
Chain IssuesNone

Trust Chain Architecture

End-Entity Certificate
CN=ruter.redirect.tetapps.com (Issuer: CN=Amazon RSA 2048 M04, O=Amazon, C=US)
Intermediate CA
CN=Amazon RSA 2048 M04, O=Amazon, C=US (Issuer: CN=Amazon Root CA 1, O=Amazon, C=US)
Root Certificate
CN=Amazon Root CA 1, O=Amazon, C=US (Issuer: CN=Amazon Root CA 1, O=Amazon, C=US)

TLS History & Relations

Everything our scans have seen for mon.ruter.no, first seen 2026-08-03; current certificate since 2026-11-07.

Certificates served

Certificate (SHA-256)IssuerValidServed
e350fc17e303dc88… current Amazon RSA 2048 M042026-11-04 → 2027-05-202026-11-07

Addresses

AddressCertificateSeen
13.227.173.19 e350fc17e303dc88… 2026-11-07
13.227.173.49 e350fc17e303dc88… 2026-11-07
13.227.173.83 e350fc17e303dc88… 2026-11-07
13.227.173.99 e350fc17e303dc88… 2026-11-07

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

Since → last checked (UTC)GradeTLSCertificatesAddresses
2026-11-07 02:50A+TLS 1.3 e350fc17e303dc88… 13.227.173.19, 13.227.173.49, 13.227.173.83, 13.227.173.99

Other domains on the same certificate

Other hosts seen on the same addresses