Skip to content

Add onyx.json with owner and records information - #47328

Open
iriss-dev wants to merge 3 commits into
is-a-dev:mainfrom
iriss-dev:onyx
Open

Add onyx.json with owner and records information#47328
iriss-dev wants to merge 3 commits into
is-a-dev:mainfrom
iriss-dev:onyx

Conversation

@iriss-dev

@iriss-dev iriss-dev commented Aug 15, 2026

Copy link
Copy Markdown
Contributor

Requirements

  • I agree to the Terms of Service.
  • My file is following the domain structure.
  • My website is reachable and completed.
  • My website is software development related.
  • My website is not for commercial use.
  • I have provided sufficient contact information in the owner key.
  • I have provided a link to my website below.

Website Preview

https://onyxos.duckdns.org

Website Purpose

ONYX is a cross-community security platform I build in my spare time.

Instead of relying on domain blocklists — which are always late, because
scam sites are renamed every week — it correlates sightings reported by
connectors and detects campaigns by their shape: the same domain
appearing across many independent communities at once, from accounts
created days earlier. A second engine looks at the order of events from
a single account to recognise attack chains.

It is written in Node with zero runtime dependencies, and the site
documents the internals: the subsystem list, the encrypted ingest channel
(SIGMA handshake, ChaCha20-Poly1305, HKDF-SHA256), and the RFC 9474 blind
signature scheme used for verdicts. There is a public search tool to check
a URL, a live threat map, and an API for connectors.

The first connector is Argos, my Discord bot, already registered at
argos.is-a.dev. ONYX is the platform behind it and deserves its own home
rather than living inside the bot's site.

It is free, has no payments, ads or accounts for sale, and I do not make
any revenue from it.
I want the onyx.is-a.dev domain

@iriss-dev
iriss-dev requested a review from a team as a code owner August 15, 2026 03:02
@is-a-dev-reviewbot

Copy link
Copy Markdown

Hi there! 👋

You've successfully made a pull request! Here are some steps to do while waiting for a maintainer to review the pull request:

  1. Check if the checks have failed or passed. You should see the status at the bottom of the pull request or a icon next to the commit ID. You can click on the 3 dots next to the "CI / Tests" check then click "View details", it will show you the logs of the tests.
  2. Check if the filename, file format, and records are valid. If you don't know if it's valid, please read this part of the documentation and use a JSON validator/formatter, like jsonlint. Make sure that the file is in the domains directory and not somewhere else in the repository.
  3. Please make sure that you've filled out the pull request template. It is generally not a good idea to overwrite the pull request template with something else unless you know what you are doing. Make sure to add either a publicly available preview of your website or a screenshot of it.
  4. Please wait patiently. Pull requests may take between a couple hours to 3 days. All of the maintainer team are volunteers and try to review the pull requests in their spare time.
  5. Please note that mentioning maintainers in pull requests without it being reviewed could lead to you getting marked as "low priority"; this also applies to pinging the maintainers in the Discord server or messaging the maintainers in private to review the pull request.

Note

If you've opened this pull request while there is a high number of other open pull requests, your wait time will be longer than usual. Please be patient!

Note

We have recently launched another free subdomain service, is-a.bot!

Claim your .is-a.bot subdomain on GitHub.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant