The site address that bob3160 gives above serves in itself a redirect address:
Re:
https://sitecheck.sucuri.net/results/creativosmexico.com.mxBut it has some serious Word Press CMS (in)security issues:
WordPress Plugins
The following plugins were detected by reading the HTML source of the WordPress sites front page.
Plugin Update Status About
wordpress-simple-paypal-shopping-cart 4.5.4 Warning latest release (4.5.9)
-https://www.tipsandtricks-hq.com/wordpress-simple-paypal-shopping-cart-plugin-768
Plugins are a source of many security vulnerabilities within WordPress installations, always keep them updated to the latest version available and check the developers plugin page for information about security related updates and fixes.
There are likely more plugins installed than those listed here as the detection method used here is passive. While these results give an indication of the status of plugin updates, a more comprehensive assessment should be undertaken by brute forcing the plugin paths using a dedicated tool.
User Enumeration
The first two user ID's were tested to determine if user enumeration is possible.
Username Name
ID: 1 not found
ID: 2 admin9
It is recommended to rename the admin user account to reduce the chance of brute force attacks occurring. As this will reduce the chance of automated password attackers gaining access. Take note that if the author archives are enabled it is usually possible to enumerate all users within a WordPress installation.
JS links checked by Google - and given the all green.
-https://creativosmexico.com.mx//s/5b99f3.js AS17378 *
-https://creativosmexico.com.mx//s/a45549.js AS17378
* seems OK ->
https://www.virustotal.com/gui/url/cbe00154cc1aca02c46396a440a66a882824509daa2508d6b415dc8122d33748?nocache=1 / but
content-script-start.js:1 seems affected (so David's remark could have hit home with this glitch).
TLS Check gives the site with the latest secure version 1.3., site is being hosted at Tierpoint, St. Louis, U.S.A.
Otto.js says no tracking scripts, no malware, no weak security on this website being detected.
On HTTP Security, found issues with no secure setting on cache-control, no CSP (content security policy) set, no best STS policy adopted, no secure attribute on PHP sessid - for cookie security, while host-only attribute however was rightly being implemented.
polonus (volunteer 3rd party cold recon website security analyst and website error-hunter)