Akamai - MS Edge SmartScreen and Google Chrome anti-typosquatting - becoming a problem

Summary:

We're starting to have real headaches with the use of Akamai as a CDN for e-Learning/rich media content.

Something appears to have changed recently within MS Edge (SmartScreen settings) and Google Chrome, with regards anti-typosquatting.

This is a safety measure to prevent someone buying a domain (e.g. fcebook.com) that people will land on when misspelling another site, e.g. facebook.com

MS Edge contains options to either proceed, or 'Don't block this site', but Chrome only has 'Ignore' or 'Go to oraclecloud.com'

The issue stems from the use of Akamai and the structure of the domains.