alink.com security report

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

69risk

Elevated

Several issues worth triaging this week.

1Critical

0High

3Medium

4Low

1Info

Collected 13 hours ago8.6sfrom cache

Certificate Transparency
DNS resolution1
Network ownership0
CDN / WAF detection0
Exposed ports & CVEs2
Registration
DNS posture3
Email authentication2
Certificate
Security headers1
Archived URLs
Analysis9

noteCertificate Transparency did not complete (HTTP 502). Results below are partial.
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 208.68.184.100 (alink.com), which advertise php 7.4.33, php 7.3.33, nginx 1.27.3. 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-2025-23419 CVE-2024-25117 CVE-2024-5458 CVE-2024-3566 CVE-2022-37454 CVE-2022-31629 CVE-2022-31628 CVE-2022-4900 CVE-2017-8923 CVE-2013-2220 CVE-2007-3205
What to do
Confirm the running versions on 208.68.184.100 and compare them against the current security release for each package before treating any single CVE as live.
CVE-2025-23419 ↗CVE-2024-25117 ↗CVE-2024-5458 ↗CVE-2024-3566 ↗CVE-2022-37454 ↗
asset: 208.68.184.100
208.68.184.100 (alink.com) reports php 7.4.33, php 7.3.33, nginx 1.27.3. 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: 208.68.184.100
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.alink.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.alink.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.alink.com/
Full URLs — including any tokens or IDs in them — are sent to every third party the page links to.
What to do
Send `Referrer-Policy: strict-origin-when-cross-origin`.
asset: https://www.alink.com/
Exact versions in response headers let anyone match the server against a CVE feed without touching it.
What to do
Strip version tokens (`ServerTokens Prod`, `server_tokens off`, remove X-Powered-By).
asset: https://www.alink.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: alink.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: alink.com

final https://www.alink.com/status 200time 4162msstack cloudflare · PHP/7.4.33 · All in One SEO (AIOSEO) 5.0.1.1

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

✓Receives mail via 1 server
mail.alink.com
!SPFends in ~all
v=spf1 mx include:spf.protection.outlook.com include:_spf.hostedemail.com ip4:208.68.0.0/16 ip4:198.181.166.86 ip4:198.181.166.11 include:sender.net include:autotask.net ~all
✓DMARCp=reject
v=DMARC1; p=reject; rua=mailto:support@alink.com; ruf=mailto:support@alink.com; fo=1; adkim=s; aspf=s;
✓MTA-STSinbound mail must use TLS

!DNSSECanswers can be forged
–CAAany CA may issue
–IPv6 (AAAA)IPv4 only
✓3 nameservers
alphans1.alink.com ns1.alink.com ns2.alink.com

✓Registered with Tucows Domains Inc.31.1 years old
alink.com
✓Registration expiry2525 days
2033-08-06
✓Transfer lock
client transfer prohibited, client update prohibited
✓2 nameservers at registry
ns1.alink.com ns2.alink.com

Address	Ports	CVEs	Edge	Network
208.68.184.100 alink.com +4	80443	11	direct	—

Archived URLs

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

alink.com security report

Elevated

Findings

Security headers

Email authentication

DNS

Registration

Hosts

Hostnames