SSL Check WHOIS
phn.com has no HTTPS: Port 443 refuses connections on its IPv4 address: no HTTPS server is running. The site is served on www.phn.com; this is its report. (phn.com checked 2026-11-22 19:45 UTC)
Dashboard / Security Report

www.phn.com

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.

www.phn.com: SSL/TLS grade A+ (HTTPS Monitor)www.phn.comA+
IPv6: no public AAAA record — the domain is reachable over IPv4 only.
A+

Exceptional Security

Overall Rating
23.60.222.91 · WHOIS ›
Assessed 2026-11-22 19:45 UTC

Grade Breakdown

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

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)
www.phn.com301 → https://www.phn.com/ → 200 OK200 OK
phn.com302 → https://www.phn.com/ → 200 OKConnection refused
  • http://www.phn.com redirects to HTTPS.
  • phn.com has no working HTTPS (connection refused): visitors who type that name do not reach the HTTPS site.

DNS Records

As a public resolver answered for www.phn.com and its domain phn.com. Looked up 2026-11-22 19:45 UTC · today

TypeRecords
www.phn.com
A
AAAA None
MX None
SPF None
phn.com
A
AAAA None
NS
edns3.ultradns.biz edns3.ultradns.com edns3.ultradns.net edns3.ultradns.org ns7.ultradns2.com ns7.ultradns2.org
MX
5 mx1.hc391-17.ca.iphmx.com 5 mx2.hc391-17.ca.iphmx.com
SPF
v=spf1 mx exists:%{i}.spf.hc391-17.ca.iphmx.com exists:%{i}.spf.hc490-56.ca.iphmx.com ip4:142.245.29.128/27 ip4:142.245.61.128/27 ip4:204.92.126.0/24 include:electric.net ~all

Certificate Properties

Type OV Organization Validated
Cert Transparency Yes (SCT)
OCSP Must Staple No
Revocation Unknown (CRL could not be downloaded) OCSP: http://ocsp.digicert.com CRL: http://crl3.digicert.com/DigiCertGlobalG2TLSRSASHA2562020CA1-1.crl
DNS CAA No (missing)
Trusted By Yes Mozilla · Apple · Android · Java · Windows
Name Match Yes
Validity Period 365 days (maximum 398 days for certificates issued then)
Chain IssuesNone

Protocol Configuration

Supported Protocols

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

Negotiated Cipher

TLS_AES_256_GCM_SHA384

Protocol Details

Connection
ALPN http/1.1
SNI Required No
Supported Named Groups X25519MLKEM768 x25519 secp256r1 (server preference order)
Post-Quantum Key Exchange Yes X25519MLKEM768
HTTP/3 (QUIC) No
Encrypted Client Hello No
Security Features
Forward SecrecyYes (ECDHE / DHE)
Downgrade Prevention Yes (legacy TLS disabled)
Secure Renegotiation Supported (RFC 5746)
Extended Master Secret Yes (RFC 7627)
OCSP Stapling Yes
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 (server-preferred order)
TLS_AES_256_GCM_SHA3840x1302ECDHEFS256Secure
TLS_CHACHA20_POLY1305_SHA2560x1303ECDHEFS256Secure
TLS_AES_128_GCM_SHA2560x1301ECDHEFS128Secure
# TLS 1.2 (server-preferred order)
TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA3840xC030ECDHEFS256Secure
TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA2560xC02FECDHEFS128Secure
TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA2560xCCA8ECDHEFS256Secure

Handshake Simulation

ClientProtocolCipher SuiteResult
Chrome 120 / Win 11TLS 1.3TLS_AES_256_GCM_SHA384 Success
Chrome 80 / Win 10TLS 1.3TLS_AES_256_GCM_SHA384 Success
Firefox 115 / Win 10TLS 1.3TLS_AES_256_GCM_SHA384 Success
iOS 17 / SafariTLS 1.3TLS_CHACHA20_POLY1305_SHA256 Success
macOS 14 / SafariTLS 1.3TLS_AES_256_GCM_SHA384 Success
Android 14TLS 1.3TLS_AES_128_GCM_SHA256 Success
Chrome 69 / Win 7TLS 1.2TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 Success
Chrome 49 / XP SP3TLS 1.2TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 Success
IE 11 / Win 10TLS 1.2TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 Success
IE 11 / Win 7TLS 1.2TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 Success
Android 9.0TLS 1.2TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 Success
Android 7.0TLS 1.2TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 Success
Android 5.0TLS 1.2TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 Success
Android 4.4.2TLS 1.2TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 Success
Java 11TLS 1.2TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 Success
Java 8u121TLS 1.2TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 Success
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.

Trust Chain Architecture

End-Entity Certificate
CN=www1.rbcinsurance.com, O=Royal Bank of Canada, L=Toronto, S=Ontario, C=CA (Issuer: CN=DigiCert Global G2 TLS RSA SHA256 2020 CA1, O=DigiCert Inc, C=US)
Intermediate CA
CN=DigiCert Global G2 TLS RSA SHA256 2020 CA1, O=DigiCert Inc, C=US (Issuer: CN=DigiCert Global Root G2, OU=www.digicert.com, O=DigiCert Inc, C=US)
Root Certificate
CN=DigiCert Global Root G2, OU=www.digicert.com, O=DigiCert Inc, C=US (Issuer: CN=DigiCert Global Root G2, OU=www.digicert.com, O=DigiCert Inc, C=US)

Certificates & Relations

The current state of www.phn.com as of our latest scan; certificate changed 2026-11-22.

Certificates served

Certificate (SHA-256)IssuerValid
feb16f6cc992bab6…DigiCert Global G2 TLS RSA SHA256 2020 CA12025-12-10 → 2026-12-09

Addresses

AddressAS
23.60.222.91 AS16625 AKAMAI-AS - Akamai Technologies, Inc.

Other domains on the same certificate