atx/registry

Contact

One person reads all of this, so pick the closest heading and it will get to the right place. Plain email, no ticket system.

Stop scanning my service

Handled first and without argument. Email from an address at the domain, or point us at a published security contact, and the domain and its subdomains go on a verified exclusion list. No justification needed, and nothing is negotiated. robots.txt works too, and we honour it.

admin@taladari.com
A finding about my service is wrong

Include the profile URL and what you believe is wrong. If you control the host, claiming it lets you correct the record and trigger a rescan yourself, which is faster than waiting on us. Corrections supersede rather than overwrite, so the record will show what we thought and when it changed.

admin@taladari.com
A vulnerability in ATX itself

Report it privately here first and we will not take issue with anything done in the course of finding it, provided you did not degrade the service or access data belonging to someone else. Expect a reply within a few days.

admin@taladari.com
Research, press, or citing the report

Every figure in the report is reproducible from its published query, and the drilldown behind each one lists the hosts it counted. If you need a cut of the data that the site does not expose, ask — it is usually one query away.

admin@taladari.com

What to expect

Opt-outs are actioned as soon as they are read. Everything else gets a real reply, though not always a fast one — see who is behind this for why. If a correction is warranted it happens in public, on the profile, as a superseding record.