Security

Netquirk Limited runs the services on the netquirk.com network. This page says where to report a security problem, what to put in the report, and what happens after you send it.

Report a problem

Write to [email protected]. Please include:

If you have already written to us, reply to that message. One thread keeps the report, our notes and the fix together.

How a report is handled

Reports are read by the team that runs the services. We answer from the same address, and the thread stays open while the report is worked on. We do not publish a response time, because we would rather tell you where a report stands than quote a deadline we cannot keep.

If a report turns out not to be a security problem, we say so and tell you what we did with it. If it is one, we fix it, and we will let you know when the fix is in place.

What to report

Anything that would let somebody else read, change or take over a Netquirk service: the DNS platform and the zones it serves, the member account and its sign-in, the pinger, virtual machines and the support desk.

An outage, a billing question or a feature request does not belong here. Open a ticket at support.netquirk.com and it reaches the right desk.

Testing a service

If you are testing a Netquirk service, tell us what you are working on and which zone or account it touches. That way we can say straight away if your test would affect other customers or the running of the service, and we can keep it clear of our own checks.

Please keep your testing to the zone or account you are working on, and leave other customers' data alone.

For automated tools

Scanners look for the RFC 9116 security.txt file at the conventional well-known path. That file carries the same address as this page, so a report reaches the same inbox either way.

The company

Netquirk Limited is registered in England and Wales (company number 16128728) with its registered office at Covent Garden, London, WC2H 9JQ. The pages on this site describe the services it runs and the terms that apply to them.