topdoglive.com security report

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

74risk

Elevated

Several issues worth triaging this week.

1Critical

0High

5Medium

3Low

2Info

Collected 3 hours ago9.9sfrom cache

Certificate Transparency8
DNS resolution8
Network ownership0
CDN / WAF detection0
Exposed ports & CVEs19
Registration
DNS posture4
Email authentication2
Certificate
Security headers3
Archived URLs
Analysis11

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 216.57.79.29 (topdoglive.com), which advertise bootstrap 3.3.7, jquery 1.10.2. 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-2020-11023 CVE-2020-11022 CVE-2019-11358 CVE-2019-8331 CVE-2018-20677 CVE-2018-20676 CVE-2018-14042 CVE-2018-14040 CVE-2016-10735 CVE-2015-9251
What to do
Confirm the running versions on 216.57.79.29 and compare them against the current security release for each package before treating any single CVE as live.
CVE-2020-11023 ↗CVE-2020-11022 ↗CVE-2019-11358 ↗CVE-2019-8331 ↗CVE-2018-20677 ↗
asset: 216.57.79.29
FTP transmits credentials in cleartext.
What to do
Restrict 21/tcp to a VPN, bastion, or allow-listed source range.
asset: 216.57.71.222:21
216.57.79.29 (topdoglive.com) reports bootstrap 3.3.7, jquery 1.10.2. 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: 216.57.79.29
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://topdoglive.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://topdoglive.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: topdoglive.com
216.57.71.222 (webdisk.topdoglive.com) reports exim 4.99.5, exim 4.99.4. 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: 216.57.71.222
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://topdoglive.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: topdoglive.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: topdoglive.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: topdoglive.com

final https://topdoglive.com/status 200time 2416msstack cloudflare · PHP/8.3.27 · WordPress 6.9.4

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

✓Receives mail via 1 server
smtp.google.com
!SPFends in ~all
v=spf1 +a +mx ip4:216.57.71.222 ip4:216.57.79.29 ip4:216.57.79.26 ip4:173.201.193.236 include:topdogtennis.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
✓4 nameservers
ns-1244.awsdns-27.org ns-1643.awsdns-13.co.uk ns-295.awsdns-36.com ns-659.awsdns-18.net

✓Registered with GoDaddy.com, LLC8.4 years old
topdoglive.com
✓Registration expiry962 days
2029-04-26
✓Transfer lock
client delete prohibited, client renew prohibited, client transfer prohibited, client update prohibited
✓4 nameservers at registry
ns-1244.awsdns-27.org ns-1643.awsdns-13.co.uk ns-295.awsdns-36.com ns-659.awsdns-18.net

Address	Ports	CVEs	Edge	Network
216.57.71.222 webdisk.topdoglive.com +8	215380110143443465587+8	0	direct	—
216.57.79.29 topdoglive.com +4	804434433	10	direct	—

Archived URLs

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

topdoglive.com security report

Elevated

Findings

Security headers

Email authentication

DNS

Registration

Hosts

Hostnames