southasiancentral.com security report

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

58risk

Elevated

Several issues worth triaging this week.

0Critical

1High

4Medium

6Low

2Info

Collected 2 hours ago20.0sfrom cache

Certificate Transparency4
DNS resolution2
Network ownership0
CDN / WAF detection0
Exposed ports & CVEs11
Registration
DNS posture2
Email authentication2
Certificate
Security headers3
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 198.60.193.26 (www.southasiancentral.com), which advertise php 8.3.33. 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-2013-2220 CVE-2007-3205
What to do
Confirm the running versions on 198.60.193.26 and compare them against the current security release for each package before treating any single CVE as live.
CVE-2013-2220 ↗CVE-2007-3205 ↗
asset: 198.60.193.26
198.60.193.26 (www.southasiancentral.com) reports php 8.3.33. 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: 198.60.193.26
FTP transmits credentials in cleartext.
What to do
Restrict 21/tcp to a VPN, bastion, or allow-listed source range.
asset: 198.60.193.26:21
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.southasiancentral.com/
Receivers are asked to report spoofing but not to block it. This is the right first step, and the wrong place to stop.
What to do
Once reports look clean, move to p=quarantine, then p=reject.
asset: southasiancentral.com
Check it is not an open relay.
What to do
Restrict 25/tcp to a VPN, bastion, or allow-listed source range.
asset: 198.60.193.26:25
staging.southasiancentral.com appears in Certificate Transparency logs. Names like this usually front staging, admin, or internal tooling, which tends to be patched later and monitored less than production.
What to do
Confirm this host is meant to be public. If not, put it behind SSO or an allow-list.
asset: staging.southasiancentral.com
www.staging.southasiancentral.com appears in Certificate Transparency logs. Names like this usually front staging, admin, or internal tooling, which tends to be patched later and monitored less than production.
What to do
Confirm this host is meant to be public. If not, put it behind SSO or an allow-list.
asset: www.staging.southasiancentral.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.southasiancentral.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: southasiancentral.com
Not urgent, but worth confirming auto-renew is on and the card on file is current.
What to do
Check auto-renew.
asset: southasiancentral.com
Mail to this domain can be downgraded to plaintext by an on-path attacker, because senders have no way to know TLS is required.
What to do
Publish an MTA-STS policy (a TXT record plus a small HTTPS-hosted file).
asset: southasiancentral.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: southasiancentral.com

final https://www.southasiancentral.com/status 200time 2376msstack cloudflare · All in One SEO Pro (AIOSEO) 5.0.1.1

✓http:// redirects to https://
✓Strict-Transport-Security
max-age=31536000; includeSubDomains; preload
✗Content-Security-Policy
✓Clickjacking protection
SAMEORIGIN
✓X-Content-Type-Options
nosniff
✗Referrer-Policy
–Permissions-Policyoptional
–security.txt publishedoptional — tells researchers where to report bugs

✓Receives mail via 5 servers
alt1.aspmx.l.google.com alt2.aspmx.l.google.com alt3.aspmx.l.google.com alt4.aspmx.l.google.com+1
✓SPFends in -all
v=spf1 a mx a:southasiancentral.com ip4:67.202.92.26 ip4:208.100.34.159 include:_spf.google.com -all
!DMARCp=none
v=DMARC1; p=none;
!MTA-STSinbound mail can be downgraded to plaintext

!DNSSECanswers can be forged
–CAAany CA may issue
–IPv6 (AAAA)IPv4 only
✓2 nameservers
bruce.ns.cloudflare.com vida.ns.cloudflare.com

✓Registered with GoDaddy.com, LLC3.8 years old
southasiancentral.com
!Registration expiry56 days
2026-11-02
✓Transfer lock
client delete prohibited, client renew prohibited, client transfer prohibited, client update prohibited
✓2 nameservers at registry
bruce.ns.cloudflare.com vida.ns.cloudflare.com

Address	Ports	CVEs	Edge	Network
198.60.193.26 www.southasiancentral.com +9	21255380110143443465+3	2	direct	—

Archived URLs

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

southasiancentral.com security report

Elevated

Findings

Security headers

Email authentication

DNS

Registration

Hosts

Hostnames