STATUS.PROTECTEDSERVICE.NET SERVER
Our parsers found that the main root page on status.protectedservice.net took five hundred milliseconds to load. Our parsers could not observe a SSL certificate, so in conclusion our crawlers consider status.protectedservice.net not secure.
Internet Protocol
199.27.180.172
SERVER OS AND ENCODING
We revealed that status.protectedservice.net is implementing the nginx os.HTML TITLE
System Status System Status informationDESCRIPTION
1750 BST Update. All services are now working and queued mail should be delivered already, or if not very shortly. 1712 BST Update. Services are being restored. We suffered a CPU failure on a VM host server and despite redundancy at every layer, this brought down our entire VM cluster we will investigate why this happened once we have successfully brought all services back online. Once again, our sincere apologies for this inconvenience. Our apologies for the inconvenience. July 6, 2015. This w.PARSED CONTENT
The web site had the following in the web site, "All services are now working and queued mail should be delivered already, or if not very shortly." We noticed that the web site stated " We suffered a CPU failure on a VM host server and despite redundancy at every layer, this brought down our entire VM cluster we will investigate why this happened once we have successfully brought all services back online." It also said " Once again, our sincere apologies for this inconvenience. Our apologies for the inconvenience."