554: link to a URL on a GMX blocklist
GMX refused the message because it contains a URL that is on one of the GMX blocklists. Remove the link or have the listing reviewed.
- GMX, WEB.DE
- Provider
- Permanent (5xx)
- Class
- Sources checked
- Author
At a glance
- Code
- 554
- Provider
- GMX, WEB.DE and mail.com
- Temporary or permanent
- PermanentRefused for good: the message comes back to the sender, and resending it gets the same answer.
- Who has to act
- The sender. The fix is on the sending side: your domain, your server or your list.
- What the server says
554 Transaction failed
What it means
GMX checks the links inside messages against its blocklists. Case r2501 means a URL in your message is on one of them, so the message is refused with 554. The listing belongs to GMX, so public URL blocklist checks may not show it. It can be your own site, or a shortener, tracking domain or image host you link to that spammers have used. GMX asks you to prevent misuse of your system, and if you think the URL was misclassified, to contact it through the form on the case page naming the URL.
Common causes
- A link in the message points to a domain or page used in spam or phishing.
- A link shortener or redirect service in the message is listed.
- A tracking domain shared with other senders of your email platform is listed.
How to fix it
- 01Check every link in the message, including tracking links and images.
- 02Remove or replace the listed link, preferably with a link on your own domain.
- 03If you think the URL is wrongly listed, contact GMX through the case page form and name the URL.
Sources
What this page rests on, checked on 20 Oct 2026. The explanation is ours; the reply text is the server's.
- GMX Postmaster case r2501: 554 Transaction failed (URL on a block list)postmaster.gmx.net
Related codes
- 554Link to a domain on the Spamhaus DBL.GMX refused the message because it links to a domain listed on the Spamhaus Domain Block List (DBL). The listing has to be resolved at Spamhaus.
- 554Transaction failed.The server permanently refused the transaction, often after receiving the message data or straight away when the connection opened.
554 at other providers
- 554Permanent rejection (554).Yahoo or AOL rejected the message for good with a 554. Yahoo uses this code for several problems, from failed authentication to unacceptable content, so the wording of the reply tells you which.
- 554Failed authentication.Yahoo or AOL refused the message because it failed the checks that confirm the sending domain, such as DKIM against the domain's policy. Yahoo lists this among its permanent 553 and 554 errors.
- 554Recipient does not exist.The Yahoo or AOL account you wrote to does not exist. The failure is permanent: check the address with the recipient, and remove it from any list.
- 554No reverse DNS (PTR) record.Xfinity refused the connection because your sending IP has no PTR record. Every server sending to Xfinity needs valid reverse DNS, so the owner of the IP must add one.
- 554No reverse DNS for your IP.IONOS refused your mail because the IP address of your mail server has no domain name assigned to it in DNS (no PTR record).
- 554Reverse DNS does not meet IONOS policy.IONOS refused your mail because the PTR record of your IP does not meet its policy, typically a generic or dynamic-looking provider name.
Further reading
All 57 GMX, WEB.DE codesEvery code in the wikiPaste your own bounce