ethdns Contact

ethdns/Abuse

Report abuse

Spam, phishing, malware, attacks or anything else harmful coming from our hosts or using our names. Tell us, and we will deal with it.

What to report here

Write to abuse@ethdns.com about anything harmful that comes from a host or a name of ours. It does not matter whether the project behind it is run by the administrators or by a third party: the report comes to us either way.

  • Spam: unsolicited mail, comment or form spam, messages in chats and forums.
  • Phishing and fraud: pages that imitate a bank, a shop, a login form or a real person.
  • Malware: files that infect computers, and servers that control infected machines.
  • Attacks: traffic floods, mass scanning, password guessing, attempts to exploit vulnerabilities.
  • Material that sexually exploits children. We remove it as soon as we learn about it. Report it to us and to the hotline in your country; the INHOPE network lists them. Do not download or forward the material itself: the address where you found it is enough.
  • Misuse of our name: forged ethdns.com senders, hosts that pretend to be ours.

Is it ours?

A name that ends in ethdns.com is ours, and so is the address such a name points to. A reverse DNS name alone is not proof: whoever controls an IP address can give it any reverse name, including one under ethdns.com.

So if a host has our name in its reverse DNS but our name does not point back to it, the host belongs to someone else. Report it to the network it belongs to (their abuse contact is in the whois record of the address), and tell us too: someone is using our name, and we want to know.

When you are not sure, send the report anyway. Checking is our job.

What to include

A good report lets us confirm the problem without writing back. For every report:

  • what happened, in a sentence or two;
  • where: the URL, hostname or IP address involved;
  • when: date and time with the time zone, UTC if possible;
  • evidence, as text.

Spam and forged mail

The full message with all its headers, attached as an .eml file or pasted as source. The “Show original” or “View source” option in most mail programs gives exactly that. A screenshot or a forwarded message loses the headers, and the headers are what we need.

Phishing and fraud

The exact URL, how you came across it (a mail, a message, an advert) and, if you have it, the message that led you there with its headers.

Attacks

Source and destination addresses, the protocol and port, the time range with its time zone, and a few lines from your logs. Many lines from one source are useful; a single blocked packet usually is not.

Malware

The URL where the file is served and, if you have it, its hash (SHA-256). Please do not attach the malware itself.

Automated reports are welcome too, including the Abuse Reporting Format (RFC 5965).

Report template

Copy it, fill in what you know, and send it to abuse@ethdns.com. Leave out what does not apply.

abuse report
Type: spam / phishing / malware / attack / other
What happened:
Where (URL, hostname or IP):
When (date, time, time zone):
How you noticed it:
Evidence (headers, log lines, hashes) below or attached:

What happens next

  1. A person reads the report and judges what it needs.
  2. We check it. If we can confirm the problem from what you sent, we move on. If not, we may ask for more.
  3. We act. A problem in our own service is fixed. A problem in a third-party project goes to its owner with a request to deal with it. When the harm is serious or ongoing, such as phishing, malware or attacks in progress, we restrict access first and talk later.
  4. We close the case. We may write back when the matter is resolved. Details about third-party projects and their owners are not shared.

There is no service-level agreement (why). ethdns is non-commercial and run by people: now and then one of us is ill or away, so a reaction can take longer than we would like. Active and serious abuse always comes first.

If you do not want your name or address passed on to the owner of the project concerned, say so in your report. We will keep it to ourselves.

What this address is not for

Last updated 1 October 2026.