https

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.4% — this entity appeared in 10 of 2,852 analyzed posts/comments in the seven days ending that day (17 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 11:45 UTCComment

   You do not need to pay for this. What GoDaddy is selling you is a paid certificate with a markup, and "review all the links" is not how SSL works: one certificate covers the whole domain, not individual pages. The standard free fix, which most of the web runs on, is Let's Encrypt: free, trusted by every browser, and it renews automatically. If the site lives on GoDaddy's shared hosting, a free SSL option is usually already included in the hosting plan (it appears as Site SSL or AutoSSL in the control panel). If it's on a VPS or a different host, the host's control panel or a tool like certbot issues the certificate for free. Here's something you can paste to your developer: "Please enable the free Let's Encrypt/AutoSSL certificate for my domain and add the redirect from HTTP to HTTPS. I'm not buying a paid certificate." Any competent developer can do this in well under an hour. If they push back on that, treat it as a red flag, because free certificates are the normal choice for a site like yours. The only cases where a paid certificate genuinely makes sense are if you need your organization's name verified in the browser (the OV/EV certificates) or your hosting setup truly cannot use Let's Encrypt, which is rare. For a normal website, $200/year is just a price tag on a certificate that exists for free.

3. 2026-10-14 02:45 UTCComment

   Quick triage: "Not Secure" in the address bar just means the page loaded over http, while a padlock with a warning triangle means you're on https but some assets are still http — right-click, Inspect, Console will list the mixed-content URLs either way. Since it's WordPress, check the GoDaddy dashboard first; they usually include a SSL cert that just needs enabling, and a plugin like Really Simple SSL will rewrite leftover http links after that. If you go the Cloudflare route, treat Flexible SSL as a stopgap — it encrypts browser to Cloudflare but not Cloudflare to your server, so switch to Full once a real cert is on the origin.

4. 2026-10-14 01:48 UTCComment

   You almost certainly do not need to pay that. Most hosts, and WordPress setups in general, can use a free Let's Encrypt certificate, so ask GoDaddy plainly whether your plan supports a free SSL certificate, and if not, moving to a host that includes one is usually cheaper. Once the certificate is on, a common leftover cause of the warning is images or links still using http, which you can fix by updating the site address to https in WordPress settings and running a search and replace on old http links.

5. 2026-10-14 01:19 UTCComment

   You do not need to pay $200 a year for this. What they are selling you bundles two separate things together. First is the certificate itself. That is what turns http into https and removes the warning. Certificates are free from Let's Encrypt, and a lot of hosts install and renew them automatically. Before paying, check your hosting control panel for an SSL or security section and see if a free certificate is already included in your plan, or if one is installed but not switched on. Second is the review all the links part. If some images or pages on your WordPress site are still saved with http addresses, the browser can keep showing a warning even after the certificate is working. That is called mixed content. Your developer can usually fix it by changing the site address to https in the WordPress settings, updating the old internal links and image addresses, and forcing the site to redirect everyone to the https version. Ask the developer who built it to do those two steps and test it in a private window afterwards. It should be a short job. If your current hosting plan genuinely will not let you use a free certificate, that is a reason to move hosts when the plan renews, not a reason to pay that fee in a panic today.