How to send a DNS over HTTPS request using Node.js and JavaScript packages. Complete code examples, configuration tutorial, and production best practices for secure DNS resolution.
primus852/traefik-ddns
This repository provides configuration files and instructions for setting up a Cloudflare Dynamic DNS (DDNS) service and a Traefik reverse proxy with Let's Encrypt SSL/TLS support. It includes Docker Compose configurations, environment variable templates, and detailed usage instructions to automate DNS updates and manage SSL certificates.
forwardemail/caldav-adapter
CalDAV server for Node.js and Koa. Modernized and maintained for @forwardemail
Requirements for HTTPS for Local Domains
When connecting to servers on their local network, users are surprised to encounter user interfaces that display errors, show insecure connections, and block some HTTP features when missing a secure context. However, obtaining PKIX certificates for those servers is difficult for a variety of reasons. This document explores requirements for authenticating local servers.
Release v0.42.0 · mswjs/interceptors
v0.42.0 (2026-07-22) Implements TCP/TLS wrap-based interception (#770) (8a8fe6f) @kettanaito ⚠️ BREAKING CHANGES Node.js v22 is the minimal supported version. getRawRequest utility has been remo...
Node.js Cryptography Overhaul: Migrating from SHA-256 to Post-Quantum Algorithms | Markaicode
Learn how to upgrade your Node.js applications from SHA-256 to quantum-resistant cryptographic algorithms with practical code examples and migration strategies.
savearoundtrip
Publish an HTTPS DNS record. Let browsers reach HTTP/3 on the first connection instead of wasting a round trip.
mitmproxy - an interactive HTTPS proxy
mitmproxy is your swiss-army knife for debugging, testing, privacy measurements, and penetration testing. It can be used to intercept, inspect, modify and replay web traffic such as HTTP/1, HTTP/2, HTTP/3, WebSockets, or any other SSL/TLS-protected protocols. You can prettify and decode a variety of message types ranging from HTML to Protobuf, intercept specific messages on-the-fly, modify them before they reach their destination, and replay them to a client or server later on.
The Core Tech Behind Datum's Desktop App
We built an app to expose your localhost to a public HTTPS URL, here's how it's built and what we learned along the way.
@atproto/oauth-client-node - AT Protocol
Node.js OAuth client for AT Protocol with built-in crypto and storage
Resolve at:// URLs · Issue #324 · AgregoreWeb/agregore-browser
We should adapt the DID handler to resolve at://{domain name here} URLs to the DID for that name. Extend the DID handler to handle the hostname just being a domain Add the did handler to resolve th...
Useful utilities and toys over DNS
Free and useful services over DNS accessible on command line
The Modern JavaScript Tutorial
Modern JavaScript Tutorial: simple, but detailed explanations with examples and tasks, including: closures, document and events, object oriented programming and more.
zeroserve: a zero-config web server you can script with eBPF
zeroserve is a small, fast, zero-config HTTPS server. You hand it a tarball of a website and it serves it - over HTTP/2 and TLS 1.3, with hot reload and a tiny resident footprint. The twist is that you can drop eBPF programs into the tarball and they run on every request, in userspace, as sandboxed middleware - rewriting, authenticating, and rate-limiting requests, or reverse-proxying them to a backend when you want it to act as a gateway in front of your app.
I've been pondering about having the browser resolve at:// URLs. I have been thinking that we could introduce a DNS-like (maybe DNS itself?) entity that goes from did:plc to URLs, the same way DNS goes from names to IP, and have the browser depend on that similar to how it depends on a DNS server.
