Get in touch
We're a small team. We read every email and try to respond within two business days.
Channels
General
Article suggestions, typo reports, general questions.
Security
Vulnerability disclosures. Private, please.
Press & podcasts
Interviews, quotes, podcast appearances.
Sponsorship
Newsletter sponsorship, sponsored content (clearly labeled).
What to email about
hello@hello@sponsors@press@security@hello@hello@Security disclosure
Found a vulnerability? Email, don't tweet.
Please don't open a public GitHub issue. Email [email protected] with a description, steps to reproduce, and the impact.
We commit to:
- · Acknowledge within 24 hours
- · Provide a fix timeline within 72 hours
- · Credit you (if you'd like) in the fix announcement
- · Not pursue legal action for good-faith research
What NOT to email about
- · Generic SEO link requests
- · Crypto / NFT pitches
- · Reselling or republishing requests
- · Guest post offers (we don't accept them)
- · "Quick chat" calendar links
- · Anything that doesn't relate to the publication
These go straight to the trash. We don't mean to be rude — we just have a small team and a lot to ship.
Elsewhere
On the record: if you need a quote for an article, please include your publication, the deadline, and the angle you're working on. We'll respond with either a quote, a referral to someone better positioned to comment, or a polite "no" if we don't have anything to add.