3 ms·
The author should have contacted the email addresses given in the DNS WHOIS (amexdns@aexp.com, gtld@aexp.com) and the obvious aliases (security@...). However I
by Nitramp 15y ago
The author should have contacted the email addresses given in the DNS WHOIS (amexdns@aexp.com, gtld@aexp.com) and the obvious aliases (security@...).
However I can understand and sympathize, it's enraging how hard it is to get into contact with a person of any kind at certain companies (KLM/Air France, I'm looking at you). I understand they want to save money, but if you run a business, you have to be contactable in one way or another. And snail mail as the last option really doesn't cut it in the 21st century.
- asto 15y agoExtremely hard to get in touch with Google as well. And you only tend to realise it when something goes horribly wrong - like when your adsense account gets suspended.
- eli 15y agoYeah, but it's not hard to report a security problem: https://www.google.com/appserve/security-bugs/new?rl=usrwf3z65ebo2rey87mtsxmr https://www.google.com/appserve/security-bugs/new?rl=usrwf3z...
- joelhaasnoot 15y agoKLM has a very good social media service department and should respond to most if not all question...
- Nitramp 15y agoI did get contacted by a Twitter account after venting there, but after DM'ing (160 characters?!) my request, they couldn't help me either. Really, why not just provide an email address? If you have someone listening and responding at @KLM in any case, why not also accept emails instead of the crippled communication possible through Twitter?
- diziet 15y agoIndeed, checking the whois for emails and other things could easily work.