{"id":16943739,"url":"https://github.com/deg4uss3r/wasm-dns-https","last_synced_at":"2026-04-30T15:32:26.957Z","repository":{"id":225882176,"uuid":"745044552","full_name":"deg4uss3r/wasm-dns-https","owner":"deg4uss3r","description":"A DNS over HTTPS example using Fastly's Compute","archived":false,"fork":false,"pushed_at":"2024-11-01T12:54:08.000Z","size":2995,"stargazers_count":1,"open_issues_count":2,"forks_count":0,"subscribers_count":1,"default_branch":"main","last_synced_at":"2025-04-05T14:43:30.021Z","etag":null,"topics":["dns","dns-over-https","fastly","networking","rust","rust-lang","wasm"],"latest_commit_sha":null,"homepage":"","language":"Rust","has_issues":true,"has_wiki":null,"has_pages":null,"mirror_url":null,"source_name":null,"license":"mit","status":null,"scm":"git","pull_requests_enabled":true,"icon_url":"https://github.com/deg4uss3r.png","metadata":{"files":{"readme":"README.md","changelog":null,"contributing":null,"funding":null,"license":"LICENSE","code_of_conduct":null,"threat_model":null,"audit":null,"citation":null,"codeowners":".github/CODEOWNERS","security":null,"support":null,"governance":null,"roadmap":null,"authors":null,"dei":null,"publiccode":null,"codemeta":null}},"created_at":"2024-01-18T14:33:30.000Z","updated_at":"2024-06-04T11:58:32.000Z","dependencies_parsed_at":"2024-05-08T02:37:57.261Z","dependency_job_id":"0670a768-1ba5-41d8-a50a-194f0f79d0bd","html_url":"https://github.com/deg4uss3r/wasm-dns-https","commit_stats":null,"previous_names":["deg4uss3r/wasm-dns-https"],"tags_count":2,"template":false,"template_full_name":null,"purl":"pkg:github/deg4uss3r/wasm-dns-https","repository_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/deg4uss3r%2Fwasm-dns-https","tags_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/deg4uss3r%2Fwasm-dns-https/tags","releases_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/deg4uss3r%2Fwasm-dns-https/releases","manifests_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/deg4uss3r%2Fwasm-dns-https/manifests","owner_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners/deg4uss3r","download_url":"https://codeload.github.com/deg4uss3r/wasm-dns-https/tar.gz/refs/heads/main","sbom_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/deg4uss3r%2Fwasm-dns-https/sbom","scorecard":null,"host":{"name":"GitHub","url":"https://github.com","kind":"github","repositories_count":286080680,"owners_count":32469344,"icon_url":"https://github.com/github.png","version":null,"created_at":"2022-05-30T11:31:42.601Z","updated_at":"2026-04-30T13:12:12.517Z","status":"ssl_error","status_checked_at":"2026-04-30T13:12:06.837Z","response_time":57,"last_error":"SSL_read: unexpected eof while reading","robots_txt_status":"success","robots_txt_updated_at":"2025-07-24T06:49:26.215Z","robots_txt_url":"https://github.com/robots.txt","online":false,"can_crawl_api":true,"host_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub","repositories_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories","repository_names_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repository_names","owners_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners"}},"keywords":["dns","dns-over-https","fastly","networking","rust","rust-lang","wasm"],"created_at":"2024-10-13T21:15:09.366Z","updated_at":"2026-04-30T15:32:26.941Z","avatar_url":"https://github.com/deg4uss3r.png","language":"Rust","funding_links":[],"categories":[],"sub_categories":[],"readme":"# wasm-dns-https\n\nThis is a personalized experiement on [Fastly Compute](https://www.fastly.com/products/compute) please do not actually use but rather enjoy the code example for now :D \n\n## How it works \n\nRight now the code works in the following way:\n\n1. The request is received via a HTTPS request (`GET` or `POST`) on the edge, and following [RFC8484](https://datatracker.ietf.org/doc/html/rfc8484).\n2. The compute code blocks domains found in the `blocklist.se` file and does not send the request upstream and then returns HTTP Status Code `418` because it's fun and a header that signifies `\"BLOCKED\"`. \n3. A domain not found in the blocklist is processed to (for now) an upstream server via HTTPS then returns to the client successfully if it exists via a forward DNS packet from the upstream Name Server (NS).\n\nMost events are logged to a [HoneyComb](https://honeycomb.io) instance, I am especially interested in learning how to optimize this to keep resoponses low. \n\n### Analysis \n\nSo far this has been working really well, I have not switched it over to my daily driver yet but here's some examples of a test site (thanks, [Can You Block It](https://canyoublockit.com)!) and it's load times: \n\n![](./docs/load_analysis.png)\n\nAs well a a full trace of the network requsts: \n\n![](./docs/example_trace.png)\n\n## Limitations\n\nRight now there's a couple limitations to this: \n\n1. I have to include the entire `blocklist.se` file for now for a couple reasons:\n    a. I could not find a decent API from the [OISD](https://oisd.nl) list or anything like it, I am happy to take recommendations!\n    b. It is too large to fit into the [Fastly Config Store](https://www.fastly.com/blog/introducing-config-store-storing-and-updating-configuration-data-at-the-edge), which is what I was hoping to use to increase performance.\n2. I am currently using the Google API as the backend/upstream Name Server, all requests are forwarded there because their [JSON API](https://developers.google.com/speed/public-dns/docs/doh/json) is nice. \n    a. Technically if a lot of people started using this service it would be private but since this is designed for just me it does give Google a bit of information (although the end requests are coming from Fastly's Compute Network IPs) of my requests. \n3. I do not have any of their privacy perserving features but that is future work for myself. \n4. Performance has not been addressed, though I am seeing decent times (thanks Rust 🦀) this is future work. \n\n## Future Work \n\nThe code is not exactly production ready, for example there's no error handling at the moment. Check in on the issues here, I plan to keep working on this until I can get it ready for use as my daily driver 😃!\n","project_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fdeg4uss3r%2Fwasm-dns-https","html_url":"https://awesome.ecosyste.ms/projects/github.com%2Fdeg4uss3r%2Fwasm-dns-https","lists_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fdeg4uss3r%2Fwasm-dns-https/lists"}