godaddy

Attention over time

7-day rolling share of analyzed posts/comments mentioning this entity · 90 daily points ending 2026-10-15

Final complete day: 2026-10-15. Attention was 0.8% — this entity appeared in 22 of 2,852 analyzed posts/comments in the seven days ending that day (26 mentions).

Each point is a seven-day rolling window of complete UTC days; a point is comparable only when at least 100 analyzed posts or comments fall inside it. A day with no analyzed records counts as zero; missing coverage is marked and never shown as zero. The series ends at the latest complete analyzed day — it never extends into the current incomplete day. How attention is measured.

Recent mentions

1. 2026-10-15 02:15 UTCComment

   GoDaddy hosting normally blocks the SMTP port at the network level, no matter how correctly you configure your plugin and credentials. Their shared and managed hosting, they block 25,465,587 by default. If you are using their products, it is ok. Follow the steps below to confirm that and get it fixed. 1. Your successful test was sent from your PC and Mac, not from the GoDaddy server. server is on a separate network. It has its own outbound rules. You cannot say the server can make the same outbound connection because of a successful connection from your pc or Mac. Use the built-in button on SMTP, "test email" and compare the results with your own. 2. The best thing to do first is ask GoDaddy whether your hosting plan has blocked outbound ports 465 and 587. 3. If it is blocked Switch to API based email service like which i mainly use Brevo, sendgrid or Mailgun. Those have free tier and WordPress plugin support. They send over HTTPS rather than the SMTP port. So it is not a WordPress plugin or WordPress issue. It is the host network-specific port which SMTP needs. And yes, it is a WordPress and GoDaddy-related hosting issue, Wordpress, WordPress\_beginners will get a specific reply too. But the answer above should work. Just tell me if it works or not.

2. 2026-10-14 19:22 UTCComment

   Not to defend GoDaddy in any way, but blocking port 25 is the default for almost any cloud provider. The spammers will take iver otherwise. Often you can just request access to use port 25, though.

3. 2026-10-14 18:07 UTCComment

   This happened to me a few months back on a client's godaddy setup, drove me up the wall til i realised they just kill those ports outright on shared plans The HTTP API route is the way to go, i ended up using a free sendgrid tier and it's been ticking along for about a year without a hiccup. Post SMTP has an API option in the settings that makes the switch pretty painless, just paste the key and you're sorted Wordfence can sometimes mess with the rest api calls too but you already had that off so i wouldn't worry about it, probably just the port block causing all the grief

4. 2026-10-14 18:05 UTCComment

   Check whether GoDaddy is blocking outbound SMTP from PHP or the hosting environment. Also enable Post SMTP’s debug log to see whether it times out during the connection, TLS handshake, or authentication. If possible, test with a transactional email provider like Brevo or SendGrid to isolate whether the issue is Yahoo-specific. SPF alone won’t fix an SMTP connection timeout

5. 2026-10-14 18:00 UTCComment

   Thank you. If GoDaddy were to go under, I’d have no problem with it. Thanks for the help.