Pinger Man is a modern uptime monitoring app we launched earlier this year. It can monitor your application as frequently as 10 seconds and send you downtime notifications via Email, SMS, Twitter, Slack and Web Hooks.
Pinger Man monitors your website from multiple locations across the world. These are used to prevent false reporting of downtime.
Pinger Man is one of the most feature packed uptime monitoring solution with advanced HTTP monitoring features such as custom HTTP headers, HTTP status code handling and HTTP authentication support.
The SSL monitoring feature automatically reminds you to renew your SSL certificates before they expire. It also tracks SSL validation failures.
Public Status Pages
Public status pages can keep your visitors informed about the status of your services. You can even use your own domain to host the status page.
Weekly reports give you a summary view about all your monitors right in your inbox.
Scheduled maintenance can be setup to exclude once or recurrent time periods from monitoring.
This morning when I tried to shop some products on Amazon.in I received the following SSL error:-
Your connection is not private
Attackers might be trying to steal your information from amazon.in (for example, passwords, messages, or credit cards). Learn more
So, I took a look at the certificate and found it to be for the domain
*.cy.peg.a2z.com instead of
Taking a look at the certificate chain, it seems that this certificate was issued by Amazon.
a2z.com is also owned by
Amazon Technologies, Inc.
Which is the same as the domain
So, everything looks okay here.
If I manually go to the Privacy Page of Amazon.in, it is serving the correct SSL certificates:-
With a much shorter certificate chain.
I also checked the domain on SSL Shopper to make sure that this isn’t something on my end.
If I ignore the certificate error, I am able to go to the
https://amazon.in page which now serves the correct certificate. Most likely, this is a deployment error and not a hack. I wonder how Amazon is serving multiple certificates for the same domain.
Update: The error is with the host
amazon.in. The www version of the domain is working fine. So, use
www.amazon.in to be safe.