buzzfeed.de security report

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

70risk

Elevated

Several issues worth triaging this week.

0Critical

2High

5Medium

5Low

2Info

Collected 19 hours ago6.5sfrom cache

Certificate Transparency10
DNS resolution15
Network ownership0
CDN / WAF detection0
Exposed ports & CVEs51
Registration
DNS posture4
Email authentication1
Certificate
Security headers0
Archived URLs
Analysis14

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.
noteNo registration data: RDAP has no record at this level.
note3 hosts were identified as CDN/edge infrastructure from ASN ownership rather than a cdncheck fingerprint.

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://www.buzzfeed.de/
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.buzzfeed.de TXT "v=DMARC1; p=none; rua=mailto:dmarc@buzzfeed.de"`, review the reports, then move to p=quarantine and p=reject.
asset: buzzfeed.de
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.buzzfeed.de/
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.buzzfeed.de/
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.buzzfeed.de/
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.buzzfeed.de/
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.buzzfeed.de/
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.buzzfeed.de/
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.buzzfeed.de/
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.buzzfeed.de/
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.buzzfeed.de/
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: buzzfeed.de
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: buzzfeed.de
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: buzzfeed.de

final https://www.buzzfeed.de/status 200time 4117msstack 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

✗Cookie cua_uuid
no Secure · no HttpOnly · no SameSite
✗Cookie new_user
no Secure · no HttpOnly · no SameSite

✓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 include:_spf.google.com ~all
✗DMARC
no record
!MTA-STSinbound mail can be downgraded to plaintext

!DNSSECanswers can be forged
–CAAany CA may issue
–IPv6 (AAAA)IPv4 only
✓4 nameservers
dns.dns1.de dns.dns2.de dns.dns3.de dns.dns4.de

Address	Ports	Edge	Network
104.26.14.31 link.buzzfeed.de +2	80443205220532082208320862087+5	Cloudflare~	—
172.67.71.184 link.buzzfeed.de +2	80443205220532082208320862087+5	Cloudflare~	—
104.26.15.31 link.buzzfeed.de +2	80443205220532082208320862087+5	Cloudflare~	—
91.234.30.113 buzzfeed.de +4	80443	direct	—
18.159.220.84 utiq.buzzfeed.de +3	80443	direct	—
52.58.107.174 utiq.buzzfeed.de +3	80443	direct	—
18.158.98.81 utiq.buzzfeed.de +2	80443	direct	—
18.155.68.104 store.buzzfeed.de +1	80	direct	—
18.155.68.66 store.buzzfeed.de +1	80	direct	—
18.155.68.112 store.buzzfeed.de +1	80	direct	—
18.155.68.9 store.buzzfeed.de +1	80	direct	—

Archived URLs

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

buzzfeed.de security report

Elevated

Findings

Security headers

Email authentication

DNS

Hosts

Hostnames