howtoaddlikebutton.com security report

Certificate, security headers, email authentication, DNS, registration, and exposed hosts — from public sources.

87risk

Critical

Exposed services or known CVEs need attention now.

1Critical

2High

6Medium

3Low

1Info

Collected 2 hours ago16.1sfrom cache

Certificate Transparency4
DNS resolution2
Network ownership0
CDN / WAF detection0
Exposed ports & CVEs2
Registration
DNS posture2
Email authentication0
Certificate
Security headers1
Archived URLs
Analysis13

noteCertificate inspection is unavailable in this runtime.
noteNetwork ownership lookup is unavailable in this runtime; ASN and org are omitted.
noteCDN/WAF detection is unavailable in this runtime.

Shodan matched these CVEs against the service banners it saw on 169.59.250.87 (www.howtoaddlikebutton.com), which advertise php 8.4.11. These are version-fingerprint matches, not confirmed exploits: a distribution may have back-ported the fix while leaving the banner unchanged. Severity reflects the volume of known issues associated with this host, not a CVSS score. CVE-2026-17544 CVE-2026-17543 CVE-2026-14355 CVE-2026-7568 CVE-2026-7263 CVE-2026-7262 CVE-2026-7261 CVE-2026-7260 CVE-2026-7259 CVE-2026-7258 CVE-2026-6735 CVE-2026-6722 CVE-2026-6104 CVE-2025-14180 CVE-2025-14179 ...and 4 more
What to do
Confirm the running versions on 169.59.250.87 and compare them against the current security release for each package before treating any single CVE as live.
CVE-2026-17544 ↗CVE-2026-17543 ↗CVE-2026-14355 ↗CVE-2026-7568 ↗CVE-2026-7263 ↗
asset: 169.59.250.87
SPF and DKIM alone do not protect the From: address a person sees. Without DMARC, a spoofed message can pass SPF for some other domain and still display yours.
What to do
Publish `_dmarc.howtoaddlikebutton.com TXT "v=DMARC1; p=none; rua=mailto:dmarc@howtoaddlikebutton.com"`, review the reports, then move to p=quarantine and p=reject.
asset: howtoaddlikebutton.com
If it lapses, the site, email, and every subdomain go dark, and the name can be taken by someone else.
What to do
Renew now and turn on auto-renew.
asset: howtoaddlikebutton.com
169.59.250.87 (www.howtoaddlikebutton.com) reports php 8.4.11. Publishing precise versions lets anyone match the host against a CVE feed without probing it, which is how targets get shortlisted for mass exploitation after a new advisory lands.
What to do
Suppress version tokens in server banners (for example `ServerTokens Prod` in Apache) and keep the packages current.
asset: 169.59.250.87
Without HSTS the browser will still try http:// first on a fresh visit, which is the window an on-path attacker uses.
What to do
Send `Strict-Transport-Security: max-age=31536000; includeSubDomains` once you are sure everything works over HTTPS.
asset: https://www.howtoaddlikebutton.com/
CSP is the main defence that limits what an injected script can do. Without it, any XSS bug is fully exploitable.
What to do
Start with a report-only policy, tighten it against the reports, then enforce.
asset: https://www.howtoaddlikebutton.com/
No X-Frame-Options or CSP frame-ancestors directive, so another site can load this page invisibly inside its own and trick users into clicking.
What to do
Send `X-Frame-Options: DENY` or `Content-Security-Policy: frame-ancestors ’none’`.
asset: https://www.howtoaddlikebutton.com/
The browser will also send this cookie over plain http://, where it can be captured.
What to do
Add `Secure` to the cookie.
asset: https://www.howtoaddlikebutton.com/
Nothing tells receiving mail servers which hosts may send as @howtoaddlikebutton.com, so anyone can. Even a domain that sends no mail should say so, or it becomes a free spoofing target.
What to do
Publish `v=spf1 -all` to state that this domain sends no mail.
asset: howtoaddlikebutton.com
Lets browsers guess content types, which turns some upload and text endpoints into script injection points.
What to do
Send `X-Content-Type-Options: nosniff` on every response.
asset: https://www.howtoaddlikebutton.com/
Without HttpOnly, any injected script can read and exfiltrate this cookie.
What to do
Add `HttpOnly` unless client-side code genuinely needs to read it.
asset: https://www.howtoaddlikebutton.com/
Answers for this domain are not signed, so a resolver cannot tell a forged response from a real one.
What to do
Enable DNSSEC at your DNS host and publish the DS record at the registrar.
asset: howtoaddlikebutton.com
Any public certificate authority may issue certificates for this domain. CAA lets you name the ones allowed to.
What to do
Add a CAA record naming your CA, e.g. `0 issue "letsencrypt.org"`.
asset: howtoaddlikebutton.com

final https://www.howtoaddlikebutton.com/status 200time 2028msstack cloudflare

✓http:// redirects to https://
✗Strict-Transport-Security
✗Content-Security-Policy
✗Clickjacking protection
✗X-Content-Type-Options
✓Referrer-Policy
origin-when-cross-origin
–Permissions-Policyoptional
–security.txt publishedoptional — tells researchers where to report bugs

✗Cookie ueid
no Secure · no HttpOnly · no SameSite

–No MX records — domain does not receive mail
✗SPF
no record
✗DMARC
no record
–MTA-STSn/a

!DNSSECanswers can be forged
–CAAany CA may issue
–IPv6 (AAAA)IPv4 only
✓2 nameservers
pdns07.domaincontrol.com pdns08.domaincontrol.com

✓Registered with GoDaddy.com, LLC10.9 years old
howtoaddlikebutton.com
✗Registration expiry30 days
2026-10-07
✓Transfer lock
client delete prohibited, client renew prohibited, client transfer prohibited, client update prohibited
✓2 nameservers at registry
pdns07.domaincontrol.com pdns08.domaincontrol.com

Address	Ports	CVEs	Edge	Network
169.59.250.87 www.howtoaddlikebutton.com +3	80443	19	direct	—

Archived URLs

Endpoints the Wayback Machine has kept — config files, backups, scripts. Slow to fetch, so it is here on request.

howtoaddlikebutton.com security report

Critical

Findings

Security headers

Email authentication

DNS

Registration

Hosts

Hostnames