tiny4k.com security report

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

57risk

Elevated

Several issues worth triaging this week.

0Critical

1High

4Medium

4Low

2Info

Collected 5 hours ago14.8sfrom cache

Certificate Transparency8
DNS resolution18
Network ownership0
CDN / WAF detection0
Exposed ports & CVEs15
Registration
DNS posture4
Email authentication2
Certificate
Security headers0
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.

A visitor who types the address without https, or follows an old link, gets the unencrypted site. On public Wi-Fi that page can be read and rewritten in transit.
What to do
Redirect every http:// request to https:// with a 301, then add HSTS.
asset: https://tiny4k.com/
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://tiny4k.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://tiny4k.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://tiny4k.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: tiny4k.com
52.202.210.106 (join.tiny4k.com) reports lua-nginx-module 1.27.1.1, openresty 1.27.1.1, phusion passenger 6.0.6. 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: 52.202.210.106
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://tiny4k.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://tiny4k.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: tiny4k.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: tiny4k.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: tiny4k.com

final https://tiny4k.com/status 403time 133msstack cloudflare

✗http:// redirects to https://
✗Strict-Transport-Security
✗Content-Security-Policy
✗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.amamultimedia.com
!SPFends in ~all
v=spf1 include:mail.amamultimedia.com ip4:208.99.76.30 ~all
!DMARCp=none
v=DMARC1; p=none; sp=none; fo=1; ri=3600; rua=mailto:ro519exg@ag.dmarcian.com
!MTA-STSinbound mail can be downgraded to plaintext

!DNSSECanswers can be forged
–CAAany CA may issue
–IPv6 (AAAA)IPv4 only
✓4 nameservers
ns-1194.awsdns-21.org ns-1631.awsdns-11.co.uk ns-301.awsdns-37.com ns-723.awsdns-26.net

✓Registered with Moniker Online Services LLC12.6 years old
tiny4k.com
✓Registration expiry149 days
2027-02-03
✓Transfer lock
client transfer prohibited
✓4 nameservers at registry
ns-1194.awsdns-21.org ns-1631.awsdns-11.co.uk ns-301.awsdns-37.com ns-723.awsdns-26.net

Address	Ports	Edge	Network
52.202.210.106 join.tiny4k.com +3	80443	direct	—
13.249.231.11 tiny4k.com +3	80443	direct	—
13.249.231.76 tiny4k.com +3	80443	direct	—
13.249.231.53 tiny4k.com +3	80443	direct	—
13.249.231.51 tiny4k.com +3	80443	direct	—
3.165.102.109 signup.tiny4k.com +3	80443	direct	—
3.165.102.77 signup.tiny4k.com +2	80	direct	—
3.165.102.104 signup.tiny4k.com +2	80	direct	—
3.165.102.60 signup.tiny4k.com +2	80	direct	—

Archived URLs

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

tiny4k.com security report

Elevated

Findings

Security headers

Email authentication

DNS

Registration

Hosts

Hostnames