buzzfeednews.com

15-check dossier · scoreboard above, section details below

Get a pack →

Scanning…

dns

info

Open standalone →

resolving…

mx

info

Open standalone →

resolving mx…

spf

info

Open standalone →

resolving spf…

dmarc

info

Open standalone →

resolving dmarc…

dkim

info

Open standalone →

probing dkim selectors…

tls

info

Open standalone →

fetching tls cert…

redirects

info

Open standalone →

tracing redirects…

headers

info

Open standalone →

fetching headers…

cors

info

Open standalone →

sending preflight…

web-surface

info

Open standalone →

inspecting web surface…

dnssec

info

Open standalone →

checking dnssec…

mta-sts

info

Open standalone →

checking mta-sts…

tls-rpt

info

Open standalone →

checking tls-rpt…

whois

info

Open standalone →

resolving whois…

ct-log

info

Open standalone →

querying CT logs…

additional context — IP + user-agent lookups

lookups that complement a dossier — useful when investigating a finding, but not part of the dossier engine itself.

IP lookup — geolocation, ASN, ISP for any IP address surfaced by the DNS or redirect sections.
user-agent parser — the browser/OS/device the request came from.
single-record DNS lookup — drill into one record type at a time.

buzzfeednews.com

15-check dossier · scoreboard above, section details below

Get a pack →

A-

Audit-ready · 4 minor advisories

Aggregate grade across 15 checks. Auditors typically flag any High-severity finding.

Pass: 11
Warn: 4
Fail: 0

What an auditor would flag first

low
DMARC
p=quarantine — receivers send to spam
SOC 2 CC6.7ISO 27001 A.13.2.1
low
DKIM
no DKIM selectors found — likely not configured
SOC 2 CC6.7
low
DNSSEC
DNSSEC not configured — no DS or DNSKEY records found
SOC 2 CC6.6ISO 27001 A.13.1.1

Need this as an artifact your auditor can verify?

Your buzzfeednews.com scan flagged 4 low findings. A signed pack covers the apex plus up to 100 CT-discovered subdomains, Ed25519-signed and ISO-timestamped, delivered in 10–30 minutes.

Get a pack →See methodology See a sample$29

Scanning…

15-check summary

DNS recordsA/AAAA records present
MX5 MX record(s) present
SPF-all hardfail — strict policy
DMARCp=quarantine — receivers send to spam
DKIMno DKIM selectors found — likely not configured
TLS certificatecert valid for 148 days
Redirect chainHTTPS served correctly
Security headers2 security header(s) missing
CORSno CORS headers — cross-origin requests blocked by default
Web surfaceHTTPS surface reachable (robots ✓, sitemap ✓, title ✗)
MTA-STSnot applicable: no _mta-sts TXT record
TLS-RPTnot applicable: no TLSRPT record
DNSSECDNSSEC not configured — no DS or DNSKEY records found
WHOISdomain expires in 60 days — renew soon
Certificate Transparencycheck failed: crt.sh: Error: crt.sh http 404; certspotter: Error: certspotter http 429

dns

info

Open standalone →

A/AAAA records present

Why it matters: Without authoritative A or AAAA records on the apex, the domain is unreachable. Missing baseline DNS shows up in vendor reviews as evidence of unmanaged infrastructure (SOC 2 CC6.6).

A: ttl=300 151.101.66.114
ttl=300 151.101.2.114
ttl=300 151.101.194.114
ttl=300 151.101.130.114
AAAA: —
NS: ttl=172800 ns-1029.awsdns-00.org.
ttl=172800 ns-118.awsdns-14.com.
ttl=172800 ns-1695.awsdns-19.co.uk.
ttl=172800 ns-595.awsdns-10.net.
SOA: ttl=900 ns-1695.awsdns-19.co.uk. awsdns-hostmaster.amazon.com. 1 7200 900 1209600 86400
CAA: —
TXT: ttl=60 "_globalsign-domain-verification=rxc48ocR2PhwobuGALz3D9ljNu6LWDgGmlBkqwbt5g"
ttl=60 "facebook-domain-verification=nzw0i4aqkjxa2km4qy9uwiuk040nl0"
ttl=60 "globalsign-domain-verification=-Q7umwx2mj164XwLa0PsoUaWe2HBhta50GjggsT98f"
ttl=60 "google-site-verification=kiZVY__GkjzXSHENpRzCiQqEsTl1tKKN__t-cesn4Tk"
ttl=60 "knowbe4-site-verification=874a4c20e9e2aa7b3811f96fed08f4ad"
ttl=60 "v=spf1 include:_spf.google.com include:shops.shopify.com include:mail.zendesk.com include:boldapps.net -all"

fetched 2026-05-23T09:35:47.136Z

dns

info

Open standalone →

resolving…

mx

info

Open standalone →

5 MX record(s) present

Why it matters: MX records direct inbound mail. Misconfiguration silently breaks email delivery and lets attackers stand up parallel MX hosts for spoofing campaigns (ISO 27001 A.8.21).

pri=1 aspmx.l.google.com.
pri=5 alt1.aspmx.l.google.com.
pri=5 alt2.aspmx.l.google.com.
pri=10 aspmx2.googlemail.com.
pri=10 aspmx3.googlemail.com.

fetched 2026-05-23T09:35:46.966Z

mx

info

Open standalone →

resolving mx…

spf

info

Open standalone →

-all hardfail — strict policy

Why it matters: SPF tells receiving servers which hosts may send mail for the domain. Without it, any sender can forge the envelope-from — the primary mechanism behind business-email-compromise (SOC 2 CC6.7).

v=spf1 include:_spf.google.com include:shops.shopify.com include:mail.zendesk.com include:boldapps.net -all

v=spf1
include:_spf.google.com
include:shops.shopify.com
include:mail.zendesk.com
include:boldapps.net
-all

fetched 2026-05-23T09:35:46.967Z

spf

info

Open standalone →

resolving spf…

dmarc

low

Open standalone →

p=quarantine — receivers send to spam

Why it matters: DMARC binds SPF and DKIM into an enforceable policy (quarantine or reject) and surfaces spoofing attempts via aggregate reports. `p=none` or absent means spoofing succeeds silently (SOC 2 CC6.7).

Recommendations

Upgrade to p=reject once your SPF and DKIM pass rates are consistently high

v=DMARC1; p=quarantine;pct=100; rua=mailto:buzzfeed+dmarc@buzzfeed.com,mailto:z81afvrt@ag.dmarcian.com; ruf=mailto:buzzfeed+dmarc@buzzfeed.com,mailto:z81afvrt@fr.dmarcian.com

v=: DMARC1
p=: quarantine
pct=: 100
rua=: mailto:buzzfeed+dmarc@buzzfeed.com,mailto:z81afvrt@ag.dmarcian.com
ruf=: mailto:buzzfeed+dmarc@buzzfeed.com,mailto:z81afvrt@fr.dmarcian.com

fetched 2026-05-23T09:35:46.968Z

dmarc

info

Open standalone →

resolving dmarc…

dkim

low

Open standalone →

no DKIM selectors found — likely not configured

Why it matters: DKIM signs outbound mail so receivers can detect tampering. Missing selectors or rotated-away keys break DMARC alignment and let receivers downgrade trust (ISO 27001 A.8.24).

Recommendations

Enable DKIM signing in your mail provider and publish the provided TXT record
Common selectors: google._domainkey, selector1._domainkey (Microsoft), mail._domainkey

no DKIM record on probed selectors (default, google, k1, selector1, selector2, mxvault)

dkim

info

Open standalone →

probing dkim selectors…

tls

info

Open standalone →

cert valid for 148 days

Why it matters: A valid current TLS certificate is the baseline for data in transit. Expiry, weak chain, or hostname mismatch break HTTPS and fail PCI 4.2.1 / SOC 2 CC6.1.

subject cn:: *.buzzfeed.com
issuer:: GlobalSign Atlas R3 DV TLS CA 2026 Q1 / GlobalSign nv-sa
valid:: Apr 2 14:03:38 2026 GMT → Oct 18 13:03:38 2026 GMT
authorized:: yes
sha256:: DE:47:23:54:4B:6E:3B:F1:64:31:A3:2D:A0:8E:B9:93:3E:1E:92:2F:8F:B3:36:52:63:EF:DB:57:CB:D9:30:F9
sans: *.buzzfeed.com
*.buzzfeed.bio
*.buzzfeednews.com
*.bzfd.bio
*.contagiousmedia.com
*.tasty.co
buzzfeed.bio
buzzfeed.com
buzzfeednews.com
bzfd.bio
contagiousmedia.com
tasty.co
www-stage.buzzfeed.com
www.buzzfeed.com
*.buzzfeed.io
*.stage.buzzfeed.com

fetched 2026-05-23T09:35:46.970Z

tls

info

Open standalone →

fetching tls cert…

redirects

info

Open standalone →

HTTPS served correctly

Why it matters: Bare HTTP requests must redirect to HTTPS without dropping the user mid-chain. Plain-text fallback or open redirects fail PCI 4.2.1 and feed phishing chains (SOC 2 CC6.6).

final status: 200 · 2 hops

[301] https://buzzfeednews.com/
[200] https://www.buzzfeednews.com/

fetched 2026-05-23T09:35:47.119Z

redirects

info

Open standalone →

tracing redirects…

headers

info

Open standalone →

2 security header(s) missing

Why it matters: Security headers — HSTS, CSP, X-Frame-Options, Referrer-Policy — defend against XSS, clickjacking, and downgrade attacks. Absent headers map directly to OWASP ASVS V14 findings (ISO 27001 A.8.23).

Recommendations

Add response header — Referrer-Policy: strict-origin-when-cross-origin
Add permissions-policy response header

final url: https://www.buzzfeednews.com/

security headers

strict-transport-security: max-age=31536000; preload
content-security-policy: upgrade-insecure-requests
x-frame-options: SAMEORIGIN
x-content-type-options: nosniff
referrer-policy: —
permissions-policy: —

other headers

accept-ranges: bytes
age: 8373
cache-control: no-cache, no-store, must-revalidate
connection: keep-alive
content-encoding: br
content-length: 66214
content-type: text/html; charset=utf-8
date: Sat, 23 May 2026 09:35:47 GMT
etag: "2c81a1b0ae1c3df223173da5657d6092cfed14b9"
expires: 0
pragma: no-cache
server: nginx
set-cookie: ccpa=true; expires=Sat, 06 Jun 2026 09:35:47 GMT; path=/; domain=www.buzzfeednews.com;
timing-allow-origin: *
vary: Accept-Encoding, X-BF-Canary, X-BF-Canary-Site-Router, X-BF-Canary-Perimeter, X-BF-Canary-Feed-UI
via: 1.1 varnish
x-cache: MISS, HIT
x-cache-hits: 0, 1
x-request-id: 398ee46d686790c1b71b5b971eb5042e
x-served-by: cache-iad-kcgs7200038-IAD, cache-iad-kcgs7200026-IAD
x-xss-protection: 1; mode=block

fetched 2026-05-23T09:35:47.104Z

headers

info

Open standalone →

fetching headers…

cors

info

Open standalone →

no CORS headers — cross-origin requests blocked by default

Why it matters: Overly permissive CORS (wildcard with credentials, or reflected origin) lets any origin read authenticated responses from this domain. OWASP A05 misconfiguration territory (NIST AC-4).

origin: https://drwho.me
method: GET
preflight status: 301

access-control-* headers

access-control-allow-origin: —
access-control-allow-methods: —
access-control-allow-headers: —
access-control-allow-credentials: —
access-control-max-age: —
access-control-expose-headers: —

no access-control-* headers returned — site does not advertise CORS to this origin

fetched 2026-05-23T09:35:47.034Z

cors

info

Open standalone →

sending preflight…

web-surface

info

Open standalone →

HTTPS surface reachable (robots ✓, sitemap ✓, title ✗)

Why it matters: Public files — robots.txt, sitemap.xml, head meta — are what attackers see first during reconnaissance. Misadvertised paths, stale sitemaps, and verbose generators leak more than intended (ISO 27001 A.8.9).

robots.txt

present

User-agent: msnbot
Crawl-delay: 120
Disallow: /*.xml$
Disallow: /category/*.xml$
Disallow: /mobile/
Disallow: *?s=mobile
Disallow: *?s=lightbox
Disallow: /buzzfeed/
Disallow: /contest
Disallow: /contests
Disallow: /plugin/
Disallow: /embed/
Disallow: /_comments/
Disallow: /bookmarks/
Disallow: /drafts/

User-agent: *
Disallow: /buzz/*.xml$
Disallow: /category/*.xml$
Disallow: /mobile/
Disallow: *?s=lightbox
Disallow: *?s=feedpager
Disallow: /buzzfeed/
Disallow: /contest
Disallow: /contests
Disallow: /_ga/
Disallow: /static/
Disallow: /dashboard/
Disallow: /plugin/
Disallow: /api/
Disallow: /buzzfeed/api/
Disallow: /embed/
Disallow: /_comments/
Disallow: /bookmarks/
Disallow: /drafts/
Disallow: /bpage-preview/
Disallow: /feed/

User-agent: Ai2Bot-Dolma
Disallow: /

User-agent: Amazonbot
Disallow: /

User-agent: anthropic-ai
Disallow: /

User-agent: Applebot-Extended
Disallow: /

User-agent: CCBot
Disallow: /

User-agent: ChatGPT-User
Disallow: /

User-agent: ClaudeBot
Disallow: /

User-agent: Claude-SearchBot
Disallow: /

User-agent: Claude-Web
Disallow: /

User-agent: Claude-User
Disallow: /

User-agent: cohere-ai
Disallow: /

User-agent: Diffbot
Disallow: /

User-agent: discobot
Disallow: /

User-agent: dotbot
Disallow: /

User-agent: FacebookBot
Disallow: /

User-agent: google-extended
Disallow: /

User-agent: Google-Extended
Disallow: /

User-agent: Googlebot
Disallow: /static-assets/

User-agent: Googlebot-Image
Allow: /*.ico$

User-agent: GPTBot
Disallow: /

User-agent: omgilibot
Disallow: /

User-agent: PerplexityBot
Disallow: /

User-agent: TurnitinBot
Disallow: /

User-agent: TtoYouBot
Disallow: /

User-agent: magpie-crawler
Disallow: /

User-agent: Slurp
Crawl-delay: 4

User-agent: yacybot
Disallow: /

User-agent: meta-externalagent
Disallow: /

User-agent: Meta-ExternalFetcher
Disallow: /

User-agent: OAI-SearchBot
Disallow: /

User-agent: Bytespider
Disallow: /

User-agent: DuckAssistBot
Disallow: /

User-agent: Perplexity-User
Disallow: /

User-agent: Timpibot
Disallow: /

User-agent: WebGPTBot
Disallow: /

User-agent: Scope3/2.0 (scope3.com)
Allow: /$
Allow: /*
Disallow: /buzz/*.xml$
Disallow: /category/*.xml$
Disallow: /mobile/
Disallow: *?s=lightbox
Disallow: *?s=feedpager
Disallow: /buzzfeed/
Disallow: /contest
Disallow: /contests
Disallow: /_ga/
Disallow: /static/
Disallow: /dashboard/
Disallow: /plugin/
Disallow: /api/
Disallow: /buzzfeed/api/
Disallow: /embed/
Disallow: /_comments/
Disallow: /bookmarks/
Disallow: /drafts/
Disallow: /bpage-preview/
Disallow: /feed/

User-agent: AmazonAdBot
Allow: /$
Allow: /*
Disallow: /buzz/*.xml$
Disallow: /category/*.xml$
Disallow: /mobile/
Disallow: *?s=lightbox
Disallow: *?s=feedpager
Disallow: /buzzfeed/
Disallow: /contest
Disallow: /contests
Disallow: /_ga/
Disallow: /static/
Disallow: /dashboard/
Disallow: /plugin/
Disallow: /api/
Disallow: /buzzfeed/api/
Disallow: /embed/
Disallow: /_comments/
Disallow: /bookmarks/
Disallow: /drafts/
Disallow: /bpage-preview/
Disallow: /feed/

Sitemap: https://www.buzzfeednews.com/sitemap/news.xml
Sitemap: https://www.buzzfeednews.com/sitemap/recent.xml
Sitemap: https://www.buzzfeednews.com/sitemap/sections.xml
Sitemap: https://www.buzzfeednews.com/sitemap/topics.xml

sitemap.xml

present — 4 url(s)

head

title: —
description: —

social

no OpenGraph or Twitter meta tags found

fetched 2026-05-23T09:35:47.157Z

web-surface

info

Open standalone →

inspecting web surface…

dnssec

low

Open standalone →

DNSSEC not configured — no DS or DNSKEY records found

Why it matters: DNSSEC cryptographically signs DNS responses, blocking cache-poisoning attacks. US federal civilian agencies are required to enable it under OMB M-22-09 (NIST SC-20).

Recommendations

Enable DNSSEC in your DNS provider's control panel and add the resulting DS record at your registrar

enabled: no
DS records: —
DNSKEY records: —

fetched 2026-05-23T09:35:47.041Z

dnssec

info

Open standalone →

checking dnssec…

mta-sts

info

Open standalone →

not applicable: no _mta-sts TXT record

Why it matters: MTA-STS forces inbound SMTP to use TLS and refuse downgraded connections. Without it, an in-path attacker can strip TLS and read mail in plaintext (SOC 2 CC6.7).

no _mta-sts TXT record

mta-sts

info

Open standalone →

checking mta-sts…

tls-rpt

info

Open standalone →

not applicable: no TLSRPT record

Why it matters: TLS-RPT publishes a reporting address for SMTP-TLS failures. Without it, downgrade attacks on inbound mail go unnoticed (SOC 2 CC7.2).

no TLSRPT record

tls-rpt

info

Open standalone →

checking tls-rpt…

whois

low

Open standalone →

domain expires in 60 days — renew soon

Why it matters: Registrar and expiry tell auditors the domain is owned, current, and not about to lapse. An expired or about-to-expire domain fails business-continuity evidence (SOC 2 A1.2).

Recommendations

Enable auto-renewal at your registrar to avoid accidental expiry

registrar: MarkMonitor Inc.
created: 2013-07-22T17:30:05Z
expires: 2026-07-22T17:30:05Z
statuses: clientDeleteProhibited https://icann.org/epp#clientDeleteProhibited, clientTransferProhibited https://icann.org/epp#clientTransferProhibited, clientUpdateProhibited https://icann.org/epp#clientUpdateProhibited

fetched 2026-05-23T09:35:47.331Z

whois

info

Open standalone →

resolving whois…

ct-log

info

Open standalone →

check failed: crt.sh: Error: crt.sh http 404; certspotter: Error: certspotter http 429

Why it matters: Every certificate issued for this domain is published in Certificate Transparency logs — including subdomains you may have forgotten. Unknown subdomains in CT are pre-disclosed attack surface (ISO 27001 A.8.16).

crt.sh: Error: crt.sh http 404; certspotter: Error: certspotter http 429

ct-log

info

Open standalone →

querying CT logs…

additional context — IP + user-agent lookups

lookups that complement a dossier — useful when investigating a finding, but not part of the dossier engine itself.

IP lookup — geolocation, ASN, ISP for any IP address surfaced by the DNS or redirect sections.
user-agent parser — the browser/OS/device the request came from.
single-record DNS lookup — drill into one record type at a time.