nowfound

Life & fun · September 30, 2018

DNS rebinding protection for Express.js

Express.js middleware for "Host" and "Referer" header validation to protect against DNS rebinding attacks. - brannondorsey/host-validation

DNS rebinding protection for Express.js launched on September 30, 2018 with 30 votes, #757 of 2,635 launches that month and more than 75% of that year's launches. The site was still online in September 2026, 8 years on.

Visit github.com ↗Alternatives

In plain words

This is DNS rebinding protection middleware for Express.js web applications. It helps developers prevent DNS rebinding attacks by validating that incoming requests match expected hostnames. The middleware is designed for anyone building web servers with Express who needs to secure their application against this type of network-level attack. It was released in 2018 and is available on GitHub.

written from the facts on this page · September 2026

Does a similar job

all alternatives →
  • DNS Rebind Toolkit2018 · github.com · ▲5

    A front-end JavaScript toolkit for creating DNS rebinding attacks. - brannondorsey/dns-rebind-toolkit

  • nextdns.io – A Combination of Cloudflare DNS and Pi-Hole2019 · nextdns.io · ▲372

    NextDNS protects you from all kinds of security threats, blocks ads and trackers on websites and in apps and provides a safe and supervised Internet for kids — on all devices and on all networks.

  • Server.js – A modern Express alternative2017 · serverjs.io · ▲295

    Powerful server for Node.js that just works so you can focus on your awesome project

  • I built a DNS resolver from scratch in Rust – no DNS librariesApr 2026 · github.com · ▲115

    I built a DNS resolver that lets me use https://frontend.numa instead of localhost:5173 — auto-generated TLS certs, WebSocket passthrough, path routing. No mkcert, no nginx, no /etc/hosts.

  • AA
    An API to provision custom hostnames with SSL2017 · ▲90

    We launched an API for custom hostnames today. A simple HTTP post with a hostname gets a temp hostname with CNAME/a record instructions, as soon as DNS is setup we issue SSL and start accepting traffic for that hostname. It's the quickest way we know of to provision custom hostnames: https://fly.io/mix/custom-hostnames/ When we started building Fly, we figured it was too late to "make SSL easy and the customers will come". Lets Encrypt changed the world, and we knew many companies rolling their own SSL support with nginx, Traefik, etc, etc. It seemed like a…

  • Fly Custom Hostnames API2017 · fly.io · ▲152

    A simple API for custom hostnames, handles DNS, SSL, etc.

More life & fun this month

the category →

Source: Show HN post ↗

Launched alongside, September 2018

the whole month →