Hi Everyone,
We have had some reports of customer accessing the Esendex
API through a misspelling of our domain name, specifically the Essendex (notice
the double s) domain name. We acquired these domain names so that if anyone
accidently went to www.essendex.com they would be redirected to the proper www.esendex.com website. Esendex recently changed the way the
re-direction works on our website and this caused problems for access to the Esendex
API if the access attempt used the Essendex domain name.
The honest answer is that we did not foresee that customers
would be using the incorrect spelling of our domain to access our API, as none
of our documentation references that spelling. I can see how it happened. It
worked, so why would anyone know any different. We can only apologise that it caused
a problem when we changed the website redirection functionality.
Esendex would like to recommend that everyone uses SSL when communicating with
our service, to protect not only your Esendex credentials but also the data you
are sending and receiving in the messages. We only provide certificates for the
esendex.com domain so you can also be sure that you're
using a supported and authentic interface.
We are proud of our reputation for performance and reliability and incidents
like this do mean a lot to us. Anything that causes an issue using our service
is a problem and we aim to reduce those to the minimum possible.
Thanks,
Esendex Operations
