How to check anything in your web stack
440 procedures for people who test software. Each one answers a single question: what to run, what the real output looks like, what a failure means, what to check next. Commands are run before they are published and the page carries the date.
Areas
- Security headers and TLS
- Performance and delivery
- API checks
- Authentication and sessions
- Accessibility
- Frontend and browser checks
- Crawlability and indexing
- Email and DNS
- CI and test suite quality
- Localization and formats
- Payments and webhooks
- WebSockets and realtime
- Logging and observability
- Databases and migrations
- Privacy and consent
- Load and stress checks
- Test environments and doubles
- File uploads and media
- Background jobs and queues
- Forms and input validation
- Data export and import
Checkers that run in your browser
- Validate JSON against a schema
- Decode a JWT and read its expiry
- Parse a cron expression and see the next runs
- Measure a contrast ratio against WCAG
- Test a regular expression and flag a pattern that can hang
- Convert a timestamp and see it in several timezones at once
- Compute an HMAC-SHA-256 webhook signature and compare it
- Read a card number: Luhn, brand, and which sandbox publishes it
Recently verified
- How to check SPF lookup limit
- How to check redirect chain
- How to test a large data export
- X-XSS-Protection deprecated
- Access log format
Checklists
- Accessibility testing checklist
- API security review
- API testing checklist
- Caching and CDN review
- Core Web Vitals audit
- Database migration checklist
- DNS migration checklist
- Email testing checklist
- File upload testing checklist
- Form validation testing checklist
- Load testing checklist
- Localization testing checklist
- Login page testing checklist
- Payment gateway testing checklist
- Pull request checklist
- Security headers review
- Test environment checklist
- TLS and certificate review
- Web performance checklist
- Website launch checklist
- Website privacy and consent review