SSL Report: ahlgp.ddns.net (47.184.26.139)
Assessed on:  Sun, 15 Jun 2025 00:37:44 UTC | Clear cache

Due to a recently discovered bug in Apple's code, your browser is exposed to MITM attacks. Click here for more information.

Summary
Overall Rating
T
If trust issues are ignored: B
0
20
40
60
80
100
Certificate
 
Protocol Support
 
Key Exchange
 
Cipher Strength
 

Visit our documentation page for more information, configuration guides, and books. Known issues are documented here.
This server's certificate is not trusted, see below for details.
This server supports TLS 1.1. Grade capped to B. MORE INFO »
This server supports TLS 1.3.  MORE INFO »
HTTP Strict Transport Security (HSTS) with long duration deployed on this server.  MORE INFO »
Certificate #1: EC 256 bits (SHA256withECDSA)
Server Key and Certificate #1
Subject ahlgp.ddns.net
Fingerprint SHA256: a6747092a7037515591ce1b6ad94b02aac28f67b46e9ce1f737628cd67c3632f
Pin SHA256: UGYun7hX+x7x63RZwdaabvt0+u2DsMx6XBX56mnZ4hs=
Common names ahlgp.ddns.net
Alternative names ahlgp.ddns.net
Serial Number 00aa495cf8
Valid from Mon, 21 Apr 2025 03:18:35 UTC
Valid until Tue, 21 Apr 2026 03:18:35 UTC (expires in 10 months and 5 days)
Key EC 256 bits
Weak key (Debian) No
Issuer ECC_GPRoot
Signature algorithm SHA256withECDSA
Extended Validation No
Certificate Transparency No
OCSP Must Staple No
Revocation information None
DNS CAA No (more info)
Trusted No   NOT TRUSTED (Why?)
Mozilla  Apple  Android  Java  Windows 


Additional Certificates (if supplied)
Certificates provided 2 (764 bytes)
Chain issues Contains anchor
#2
Subject ECC_GPRoot   Not in trust store
Fingerprint SHA256: 476a1f031e4777498e9456350238abf9786c36086ed4c69143de217b64290bbe
Pin SHA256: QWBVC/eyU0ZS/ODviMdHQ5SFk/uiNaf1qJAP6oQGxHQ=
Valid until Tue, 21 Apr 2026 03:17:47 UTC (expires in 10 months and 5 days)
Key EC 256 bits
Issuer ECC_GPRoot   Self-signed
Signature algorithm SHA256withECDSA


Certification Paths
Path #1: Not trusted (path does not chain to a trusted anchor)
1 Sent by server ahlgp.ddns.net
Fingerprint SHA256: a6747092a7037515591ce1b6ad94b02aac28f67b46e9ce1f737628cd67c3632f
Pin SHA256: UGYun7hX+x7x63RZwdaabvt0+u2DsMx6XBX56mnZ4hs=

EC 256 bits / SHA256withECDSA
2 Sent by server
  Not in trust store
ECC_GPRoot   Self-signed
Fingerprint SHA256: 476a1f031e4777498e9456350238abf9786c36086ed4c69143de217b64290bbe
Pin SHA256: QWBVC/eyU0ZS/ODviMdHQ5SFk/uiNaf1qJAP6oQGxHQ=

EC 256 bits / SHA256withECDSA
Path #1: Not trusted (path does not chain to a trusted anchor)
1 Sent by server ahlgp.ddns.net
Fingerprint SHA256: a6747092a7037515591ce1b6ad94b02aac28f67b46e9ce1f737628cd67c3632f
Pin SHA256: UGYun7hX+x7x63RZwdaabvt0+u2DsMx6XBX56mnZ4hs=

EC 256 bits / SHA256withECDSA
2 Sent by server
  Not in trust store
ECC_GPRoot   Self-signed
Fingerprint SHA256: 476a1f031e4777498e9456350238abf9786c36086ed4c69143de217b64290bbe
Pin SHA256: QWBVC/eyU0ZS/ODviMdHQ5SFk/uiNaf1qJAP6oQGxHQ=

EC 256 bits / SHA256withECDSA
Path #1: Not trusted (path does not chain to a trusted anchor)
1 Sent by server ahlgp.ddns.net
Fingerprint SHA256: a6747092a7037515591ce1b6ad94b02aac28f67b46e9ce1f737628cd67c3632f
Pin SHA256: UGYun7hX+x7x63RZwdaabvt0+u2DsMx6XBX56mnZ4hs=

EC 256 bits / SHA256withECDSA
2 Sent by server
  Not in trust store
ECC_GPRoot   Self-signed
Fingerprint SHA256: 476a1f031e4777498e9456350238abf9786c36086ed4c69143de217b64290bbe
Pin SHA256: QWBVC/eyU0ZS/ODviMdHQ5SFk/uiNaf1qJAP6oQGxHQ=

EC 256 bits / SHA256withECDSA
Path #1: Not trusted (path does not chain to a trusted anchor)
1 Sent by server ahlgp.ddns.net
Fingerprint SHA256: a6747092a7037515591ce1b6ad94b02aac28f67b46e9ce1f737628cd67c3632f
Pin SHA256: UGYun7hX+x7x63RZwdaabvt0+u2DsMx6XBX56mnZ4hs=

EC 256 bits / SHA256withECDSA
2 Sent by server
  Not in trust store
ECC_GPRoot   Self-signed
Fingerprint SHA256: 476a1f031e4777498e9456350238abf9786c36086ed4c69143de217b64290bbe
Pin SHA256: QWBVC/eyU0ZS/ODviMdHQ5SFk/uiNaf1qJAP6oQGxHQ=

EC 256 bits / SHA256withECDSA
Path #1: Not trusted (path does not chain to a trusted anchor)
1 Sent by server ahlgp.ddns.net
Fingerprint SHA256: a6747092a7037515591ce1b6ad94b02aac28f67b46e9ce1f737628cd67c3632f
Pin SHA256: UGYun7hX+x7x63RZwdaabvt0+u2DsMx6XBX56mnZ4hs=

EC 256 bits / SHA256withECDSA
2 Sent by server
  Not in trust store
ECC_GPRoot   Self-signed
Fingerprint SHA256: 476a1f031e4777498e9456350238abf9786c36086ed4c69143de217b64290bbe
Pin SHA256: QWBVC/eyU0ZS/ODviMdHQ5SFk/uiNaf1qJAP6oQGxHQ=

EC 256 bits / SHA256withECDSA

Click here to expand

Configuration
Protocols
TLS 1.3 Yes
TLS 1.2 Yes
TLS 1.1 Yes
TLS 1.0 No
SSL 3 No
SSL 2 No


Cipher Suites
# TLS 1.3 (server has no preference)
TLS_AES_128_GCM_SHA256 (0x1301)   ECDH x25519 (eq. 3072 bits RSA)   FS 128
TLS_AES_256_GCM_SHA384 (0x1302)   ECDH x25519 (eq. 3072 bits RSA)   FS 256
TLS_CHACHA20_POLY1305_SHA256 (0x1303)   ECDH x25519 (eq. 3072 bits RSA)   FS 256
# TLS 1.2 (suites in server-preferred order)
TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384 (0xc02c)   ECDH secp256r1 (eq. 3072 bits RSA)   FS 256
TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 (0xc02b)   ECDH secp256r1 (eq. 3072 bits RSA)   FS 128
TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384 (0xc024)   ECDH secp256r1 (eq. 3072 bits RSA)   FS   WEAK 256
TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256 (0xc023)   ECDH secp256r1 (eq. 3072 bits RSA)   FS   WEAK 128
TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA (0xc00a)   ECDH secp256r1 (eq. 3072 bits RSA)   FS   WEAK 256
TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA (0xc009)   ECDH secp256r1 (eq. 3072 bits RSA)   FS   WEAK 128
# TLS 1.1 (suites in server-preferred order)
TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA (0xc00a)   ECDH secp256r1 (eq. 3072 bits RSA)   FS   WEAK 256
TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA (0xc009)   ECDH secp256r1 (eq. 3072 bits RSA)   FS   WEAK 128


Handshake Simulation
Android 4.4.2 EC 256 (SHA256)   TLS 1.2 TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384   ECDH secp256r1  FS
Android 5.0.0 EC 256 (SHA256)   TLS 1.2 TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256   ECDH secp256r1  FS
Android 6.0 EC 256 (SHA256)   TLS 1.2 TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256   ECDH secp256r1  FS
Android 7.0 EC 256 (SHA256)   TLS 1.2 TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384   ECDH secp256r1  FS
Android 8.0 EC 256 (SHA256)   TLS 1.2 TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384   ECDH secp256r1  FS
Android 8.1 -   TLS 1.3 TLS_CHACHA20_POLY1305_SHA256   ECDH x25519  FS
Android 9.0 -   TLS 1.3 TLS_CHACHA20_POLY1305_SHA256   ECDH x25519  FS
BingPreview Jan 2015 EC 256 (SHA256)   TLS 1.2 TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384   ECDH secp256r1  FS
Chrome 49 / XP SP3 Server sent fatal alert: illegal_parameter
Chrome 69 / Win 7  R EC 256 (SHA256)   TLS 1.2 TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384   ECDH secp256r1  FS
Chrome 70 / Win 10 -   TLS 1.3 TLS_AES_128_GCM_SHA256   ECDH x25519  FS
Chrome 80 / Win 10  R -   TLS 1.3 TLS_AES_128_GCM_SHA256   ECDH x25519  FS
Firefox 31.3.0 ESR / Win 7 EC 256 (SHA256)   TLS 1.2 TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256   ECDH secp256r1  FS
Firefox 47 / Win 7  R EC 256 (SHA256)   TLS 1.2 TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256   ECDH secp256r1  FS
Firefox 49 / XP SP3 EC 256 (SHA256)   TLS 1.2 TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384   ECDH secp256r1  FS
Firefox 62 / Win 7  R EC 256 (SHA256)   TLS 1.2 TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384   ECDH secp256r1  FS
Firefox 73 / Win 10  R -   TLS 1.3 TLS_AES_128_GCM_SHA256   ECDH x25519  FS
Googlebot Feb 2018 EC 256 (SHA256)   TLS 1.2 TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384   ECDH secp256r1  FS
IE 11 / Win 7  R EC 256 (SHA256)   TLS 1.2 TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384   ECDH secp256r1  FS
IE 11 / Win 8.1  R EC 256 (SHA256)   TLS 1.2 TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384   ECDH secp256r1  FS
IE 11 / Win Phone 8.1  R EC 256 (SHA256)   TLS 1.2 TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384   ECDH secp256r1  FS
IE 11 / Win Phone 8.1 Update  R EC 256 (SHA256)   TLS 1.2 TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384   ECDH secp256r1  FS
IE 11 / Win 10  R EC 256 (SHA256)   TLS 1.2 TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384   ECDH secp256r1  FS
Edge 15 / Win 10  R EC 256 (SHA256)   TLS 1.2 TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384   ECDH secp256r1  FS
Edge 16 / Win 10  R EC 256 (SHA256)   TLS 1.2 TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384   ECDH secp256r1  FS
Edge 18 / Win 10  R EC 256 (SHA256)   TLS 1.2 TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384   ECDH secp256r1  FS
Edge 13 / Win Phone 10  R EC 256 (SHA256)   TLS 1.2 TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384   ECDH secp256r1  FS
Java 8u161 EC 256 (SHA256)   TLS 1.2 TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384   ECDH secp256r1  FS
Java 11.0.3 -   TLS 1.3 TLS_AES_128_GCM_SHA256   ECDH secp256r1  FS
Java 12.0.1 -   TLS 1.3 TLS_AES_128_GCM_SHA256   ECDH secp256r1  FS
OpenSSL 1.0.1l  R EC 256 (SHA256)   TLS 1.2 TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384   ECDH secp256r1  FS
OpenSSL 1.0.2s  R EC 256 (SHA256)   TLS 1.2 TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384   ECDH secp256r1  FS
OpenSSL 1.1.0k  R EC 256 (SHA256)   TLS 1.2 TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384   ECDH secp256r1  FS
OpenSSL 1.1.1c  R -   TLS 1.3 TLS_AES_256_GCM_SHA384   ECDH x25519  FS
Safari 6 / iOS 6.0.1 EC 256 (SHA256)   TLS 1.2 TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384   ECDH secp256r1  FS
Safari 7 / iOS 7.1  R EC 256 (SHA256)   TLS 1.2 TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384   ECDH secp256r1  FS
Safari 7 / OS X 10.9  R EC 256 (SHA256)   TLS 1.2 TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384   ECDH secp256r1  FS
Safari 8 / iOS 8.4  R EC 256 (SHA256)   TLS 1.2 TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384   ECDH secp256r1  FS
Safari 8 / OS X 10.10  R EC 256 (SHA256)   TLS 1.2 TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384   ECDH secp256r1  FS
Safari 9 / iOS 9  R EC 256 (SHA256)   TLS 1.2 TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384   ECDH secp256r1  FS
Safari 9 / OS X 10.11  R EC 256 (SHA256)   TLS 1.2 TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384   ECDH secp256r1  FS
Safari 10 / iOS 10  R EC 256 (SHA256)   TLS 1.2 TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384   ECDH secp256r1  FS
Safari 10 / OS X 10.12  R EC 256 (SHA256)   TLS 1.2 TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384   ECDH secp256r1  FS
Safari 12.1.2 / MacOS 10.14.6 Beta  R -   TLS 1.3 TLS_CHACHA20_POLY1305_SHA256   ECDH x25519  FS
Safari 12.1.1 / iOS 12.3.1  R -   TLS 1.3 TLS_CHACHA20_POLY1305_SHA256   ECDH x25519  FS
Apple ATS 9 / iOS 9  R EC 256 (SHA256)   TLS 1.2 TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384   ECDH secp256r1  FS
Yahoo Slurp Jan 2015 EC 256 (SHA256)   TLS 1.2 TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384   ECDH secp256r1  FS
YandexBot Jan 2015 EC 256 (SHA256)   TLS 1.2 TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384   ECDH secp256r1  FS
# Not simulated clients (Protocol mismatch)
Android 2.3.7   No SNI 2 Protocol mismatch (not simulated)
Android 4.0.4 Protocol mismatch (not simulated)
Android 4.1.1 Protocol mismatch (not simulated)
Android 4.2.2 Protocol mismatch (not simulated)
Android 4.3 Protocol mismatch (not simulated)
Baidu Jan 2015 Protocol mismatch (not simulated)
IE 6 / XP   No FS 1   No SNI 2 Protocol mismatch (not simulated)
IE 7 / Vista Protocol mismatch (not simulated)
IE 8 / XP   No FS 1   No SNI 2 Protocol mismatch (not simulated)
IE 8-10 / Win 7  R Protocol mismatch (not simulated)
IE 10 / Win Phone 8.0 Protocol mismatch (not simulated)
Java 6u45   No SNI 2 Protocol mismatch (not simulated)
Java 7u25 Protocol mismatch (not simulated)
OpenSSL 0.9.8y Protocol mismatch (not simulated)
Safari 5.1.9 / OS X 10.6.8 Protocol mismatch (not simulated)
Safari 6.0.4 / OS X 10.8.4  R Protocol mismatch (not simulated)

Click here to expand

(1) Clients that do not support Forward Secrecy (FS) are excluded when determining support for it.
(2) No support for virtual SSL hosting (SNI). Connects to the default site if the server uses SNI.
(3) Only first connection attempt simulated. Browsers sometimes retry with a lower protocol version.
(R) Denotes a reference browser or client, with which we expect better effective security.
(All) We use defaults, but some platforms do not use their best protocols and features (e.g., Java 6 & 7, older IE).
(All) Certificate trust is not checked in handshake simulation, we only perform TLS handshake.


Protocol Details
Secure Renegotiation Supported
Secure Client-Initiated Renegotiation No
Insecure Client-Initiated Renegotiation No
BEAST attack Mitigated server-side (more info)  
POODLE (SSLv3) No, SSL 3 not supported (more info)
POODLE (TLS) No (more info)
Zombie POODLE No (more info)   TLS 1.2 : 0xc023
GOLDENDOODLE No (more info)   TLS 1.2 : 0xc023
OpenSSL 0-Length No (more info)   TLS 1.2 : 0xc023
Sleeping POODLE No (more info)   TLS 1.2 : 0xc023
Downgrade attack prevention No, TLS_FALLBACK_SCSV not supported (more info)
SSL/TLS compression No
RC4 No
Heartbeat (extension) No
Heartbleed (vulnerability) No (more info)
Ticketbleed (vulnerability) No (more info)
OpenSSL CCS vuln. (CVE-2014-0224) No (more info)
OpenSSL Padding Oracle vuln.
(CVE-2016-2107)
No (more info)
ROBOT (vulnerability) No (more info)
Forward Secrecy Yes (with most browsers)   ROBUST (more info)
ALPN No
NPN No
Session resumption (caching) Yes
Session resumption (tickets) No
OCSP stapling No
Strict Transport Security (HSTS) Yes
max-age=31536000;
HSTS Preloading Not in: Chrome  Edge  Firefox  IE 
Public Key Pinning (HPKP) No (more info)
Public Key Pinning Report-Only No
Public Key Pinning (Static) No (more info)
Long handshake intolerance No
TLS extension intolerance No
TLS version intolerance No
Incorrect SNI alerts No
Uses common DH primes No, DHE suites not supported
DH public server param (Ys) reuse No, DHE suites not supported
ECDH public server param reuse No
Supported Named Groups secp256r1
SSL 2 handshake compatibility Yes
0-RTT enabled No


HTTP Requests
1 https://ahlgp.ddns.net/  (HTTP/1.1 302 Found)
1
Date Sun, 15 Jun 2025 00:36:45 GMT
Content-Type text/html; charset=UTF-8
Content-Length 173
Connection close
Cache-Control no-store, no-cache, must-revalidate, post-check=0, pre-check=0
Location /global-protect/login.esp
Set-Cookie SESSID=507ed2a1-97bd-4dd0-bef1-45210ba419b5; Path=/; SameSite=Lax; HttpOnly; Secure
X-Frame-Options DENY
Strict-Transport-Security max-age=31536000;
X-XSS-Protection 1; mode=block
X-Content-Type-Options nosniff
Content-Security-Policy default-src 'self'; script-src 'self' 'unsafe-inline'; img-src * data:; style-src 'self' 'unsafe-inline';
2 https://ahlgp.ddns.net/global-protect/login.esp  (HTTP/1.1 404 Not Found)
2
Date Sun, 15 Jun 2025 00:36:45 GMT
Content-Type text/html; charset=UTF-8
Content-Length 74
Connection close
Cache-Control no-store, no-cache, must-revalidate, post-check=0, pre-check=0
Set-Cookie SESSID=c8f6a33a-4581-4719-86b3-b8aa1ebb90eb; Path=/; SameSite=Lax; HttpOnly; Secure
X-Frame-Options DENY


Miscellaneous
Test date Sun, 15 Jun 2025 00:36:33 UTC
Test duration 71.499 seconds
HTTP status code 404
HTTP server signature -
Server hostname 47-184-26-139.fdr02.crtn.tx.ip.frontiernet.net


Why is my certificate not trusted?

There are many reasons why a certificate may not be trusted. The exact problem is indicated on the report card in bright red. The problems fall into three categories:

  1. Invalid certificate
  2. Invalid configuration
  3. Unknown Certificate Authority

1. Invalid certificate

A certificate is invalid if:

2. Invalid configuration

In some cases, the certificate chain does not contain all the necessary certificates to connect the web server certificate to one of the root certificates in our trust store. Less commonly, one of the certificates in the chain (other than the web server certificate) will have expired, and that invalidates the entire chain.

3. Unknown Certificate Authority

In order for trust to be established, we must have the root certificate of the signing Certificate Authority in our trust store. SSL Labs does not maintain its own trust store; instead we use the store maintained by Mozilla.

If we mark a web site as not trusted, that means that the average web user's browser will not trust it either. For certain special groups of users, such web sites can still be secure. For example, if you can securely verify that a self-signed web site is operated by a person you trust, then you can trust that self-signed web site too. Or, if you work for an organisation that manages its own trust, and you have their own root certificate already embedded in your browser. Such special cases do not work for the general public, however, and this is what we indicate on our report card.

4. Interoperability issues

In some rare cases trust cannot be established because of interoperability issues between our code and the code or configuration running on the server. We manually review such cases, but if you encounter such an issue please feel free to contact us. Such problems are very difficult to troubleshoot and you may be able to provide us with information that might help us determine the root cause.

SSL Report v2.4.0