queue.wxt.dev returns NXDOMAIN
Open
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 10
- Forks
- 3
- PR merge metrics
- No merged PRs in 30d
Description
The "Who's Using WXT?" section on https://wxt.dev/ currently shows "Failed to load extension details."
The browser console reports:
TypeError: Failed to fetch
As of 2026-08-26 07:20 UTC, queue.wxt.dev returns NXDOMAIN from both the authoritative nameserver and public DNS resolvers:
$ dig @mira.ns.cloudflare.com queue.wxt.dev A +noall +answer +authority +comments
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN
$ dig @1.1.1.1 queue.wxt.dev A +noall +answer +authority +comments
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by checking the DNS configuration for queue.wxt.dev and reproduce the NXDOMAIN response with the dig commands in the issue. Verify that the endpoint resolves and that the “Who’s Using WXT?” section no longer reports a failed fetch.
Written by the indexing model from the issue text.
Assessment
- Domain
- api, infrastructure
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 45/100