Invalid Security Certificate of airvpn.org

[guido.arellano 0]

When I tried to visit your home page https://airvpn.org using Firefox to check my remaining subscription, I got a warning message that your site's security certificate is invalid. Even if I continue and add an exception, it doesn't go through and I keep on being forwarded to "Parallels" which tells me AirVPN is not available. I tried all available browsers in my system and I get the same result. Even if I login to the VPN service using the AirVPN client and repeat the process, I still can't access your home page https://airvpn.org. Finally, I tried connecting to the Tor Network and I was able to visit your home page again, login, and send this inquiry.

Has my ISP somehow found a way to prevent me from accessing your site? Or is another malicious entity lurking in my system which prevents me from doing so? Or could I have an error in my Comodo firewall settings?

[Staff 9972]

When I tried to visit your home page https://airvpn.org using Firefox to check my remaining subscription, I got a warning message that your site's security certificate is invalid. Even if I continue and add an exception, it doesn't go through and I keep on being forwarded to "Parallels" which tells me AirVPN is not available. I tried all available browsers in my system and I get the same result. Even if I login to the VPN service using the AirVPN client and repeat the process, I still can't access your home page https://airvpn.org. Finally, I tried connecting to the Tor Network and I was able to visit your home page again, login, and send this inquiry.

Hello!

It's good that you access our website through TOR. The TOR browser did not give you any certificate warning about our website, right?

The certificate is emitted by a proper CA which is correctly recognized on every browser. You should check the certificate of the site where you get the warning, it might not be our real website.

Please check the fingerprint of the certificate to verify whether you're really on our website or not:

SHA-256 fingerprint: 7F C6 1C D8 97 F9 51 EC 3B D5 84 F0 4F BD E3 2D DB 3D F8 12 16 C8 86 BB A0 EA 26 31 36 35 21 8E

SHA-1 fingerprint: EE 54 D8 0A E5 68 DB 61 69 51 E7 0B BF C6 E8 D1 0C EC 86 3F

airvpn.org must resolve to 212.117.180.25

If your DNS is "poisoned", try to use another one, or anyway put in your hosts file the line:

212.117.180.25 airvpn,org

If it's the IP address that is blocked, you can access our alternative frontend 85.17.207.151. Insert in your hosts file the line:

85.17.207.151 airvpn.org

Check the Comodo rules and make sure they allow access to airvpn.org

You can determine whether an IP address of our frontend servers is blocked on your system for example by trying to ping it directly:

ping 85.17.207.151

ping 212.117.180.25

Anyway, using TOR is a very good solution.

Has my ISP somehow found a way to prevent me from accessing your site? Or is another malicious entity lurking in my system which prevents me from doing so? Or could I have an error in my Comodo firewall settings?

Poor quality programs like Malwarebytes can prevent access to our website because they block whole datacenter IP ranges.

Kind regards

[guido.arellano 0]

Yes, TOR is the only way I can access the AirVPN site right now.

My hosts file already contained 85.17.207.151 and 46.105.19.36, and so I added 212.118.180.25. When I pinged your front-end servers as you suggested I got the following:

Pinging 85.17.207.151 with 32 bytes of data:

Reply from 85.17.207.151: bytes=32 time=282ms TTL=48

Reply from 85.17.207.151: bytes=32 time=297ms TTL=48

Reply from 85.17.207.151: bytes=32 time=294ms TTL=48

Reply from 85.17.207.151: bytes=32 time=295ms TTL=48

Ping statistics for 85.17.207.151:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 282ms, Maximum = 297ms, Average = 292ms

Pinging 212.118.180.25 with 32 bytes of data:

Reply from 212.9.160.65: TTL expired in transit.

Reply from 212.9.160.65: TTL expired in transit.

Reply from 212.9.160.65: TTL expired in transit.

Reply from 212.9.160.65: TTL expired in transit.

Ping statistics for 212.118.180.25:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

So what might be the problem here?

(I also attached a screen shot of the Global Rules of Network Security Policy in Comodo for reference)

[Staff 9972]

Yes, TOR is the only way I can access the AirVPN site right now.

My hosts file already contained 85.17.207.151 and 46.105.19.36,

Hello!

Please delete the 46.105.19.36 entry, this IP is no more used by us.

and so I added 212.118.180.25. When I pinged your front-end servers as you suggested I got the following:

Pinging 85.17.207.151 with 32 bytes of data:

Reply from 85.17.207.151: bytes=32 time=282ms TTL=48

Reply from 85.17.207.151: bytes=32 time=297ms TTL=48

Reply from 85.17.207.151: bytes=32 time=294ms TTL=48

Reply from 85.17.207.151: bytes=32 time=295ms TTL=48

Ping statistics for 85.17.207.151:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 282ms, Maximum = 297ms, Average = 292ms

Pinging 212.118.180.25 with 32 bytes of data:

Reply from 212.9.160.65: TTL expired in transit.

Reply from 212.9.160.65: TTL expired in transit.

Reply from 212.9.160.65: TTL expired in transit.

Reply from 212.9.160.65: TTL expired in transit.

Ping statistics for 212.118.180.25:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

So what might be the problem here?

(I also attached a screen shot of the Global Rules of Network Security Policy in Comodo for reference)

The Comodo rules are fine.

Please check the IP address of the frontend, it's 212.117.180.25. We apologize for the previous mistyping, which anyway does not explain your previous problem.

In the meantime, leave in your hosts file only the following entry for airvpn.org:

85.17.207.151 airvpn.org

What about the certificate fingerpring check? Is it ok or not?

Kind regards