ChrisPackard
UPDATE: February 23rd @14:43 GMT
You may still experience issues with Page Checker where elements appear to be blocked (see screenshot below as an example).
Google have removed the api.digitalqualitymanager.com domain from it's unsafe browsing list - see https://transparencyreport.google.com/safe-browsing/search?url=https:%2F%2Fapi.digitalqualitymanager...
Some 3rd party products, such as virus scanners, also use Google's unsafe browsing list to block sites. These 3rd party products refresh their list periodically so the domain should fall off eventually. If you continue to experience issues with Page Checker being blocked by your virus scanner, please liaise with your internal IT department to get the domain removed from it.
UPDATE: February 14th @ 11:27 GMT
Page Checker is fully operational again. After contacting Google, Page Checker is no longer being blocked or reported as "unsafe".
February 10th @ 12:10 GMT
When using Page Checker in Google Chrome, Google prevents Page Checker from running and displays a message “Deceptive site ahead."
When using Page Checker in Google Chrome, Google prevents Page Checker from running and displays a message “Deceptive site ahead. Attackers on api.digitalqualitymanager.com may trick you into doing something dangerous like installing software or revealing your personal information (for example, passwords, phone numbers, or credit cards).”
The domain we use to run our API calls for Page Checker, api.digitalqualitymanager.com, has been suggested as “unsafe”, and Google automatically blocks the URL from running
Is DQM Page Checker unsafe?
No. No changes have been made to the way Page checker works, the domain used is owned by Crownpeak and is secured. We are working to understand why Google has suddenly flagged this.
How are we fixing the issue?
We are in contact with Google to request a review to mark our domain as safe again.
Can I still use Page Checker?
Yes. We can confirm that there is no issue with the domain api.digitalqualitymanager.com. Other browsers work without this issue (e.g. Firefox).