Skip to content
IONOS (1&1) · permanent error

554: no 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).

IONOS
Provider
Permanent (5xx)
Class
Sources checked
Author

At a glance

Code
554
Provider
IONOS (1&1)
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 Invalid DNS PTR resource record

What it means

Reverse DNS maps an IP address back to a name through a PTR record. IONOS requires one for every server that delivers mail to its customers. This 554 means your sending IP has none, so the mail is refused. The remedy IONOS gives is short: add the missing DNS entry. The PTR record is managed by whoever owns the IP range, usually your hosting provider or ISP, not in your domain DNS. Choose a name in your own domain that resolves back to the same IP.

Common causes

  • No PTR record was created for the sending IP.
  • The server moved to a new IP and reverse DNS was not set up for it.

How to fix it

  1. 01Ask the owner of the IP range (your host or ISP) to add a PTR record for the IP.
  2. 02Use a fully qualified name in your domain, such as mail.yourdomain.tld, that resolves back to the IP.
  3. 03Retry delivery once the record is published.

Sources

What this page rests on, checked on 20 Oct 2026. The explanation is ours; the reply text is the server's.

  1. 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.IONOSPermanent
  2. 554No reverse DNS for your IP.GMX refused the connection because the IP address of your mail server has no PTR record, so it is not tied to any domain name in DNS.GMX, WEB.DEPermanent
  3. 554Transaction failed.The server permanently refused the transaction, often after receiving the message data or straight away when the connection opened.StandardPermanent

554 at other providers

  1. 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.YahooPermanent
  2. 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.YahooPermanent
  3. 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.YahooPermanent
  4. 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.ComcastPermanent
  5. 554Rejected for breaking GMX guidelines.GMX refused the message permanently because the connection broke its guidelines. GMX points to its requirements page and asks for the full error message if the problem continues.GMX, WEB.DEPermanent
  6. 554IP address on the GMX blocklist.Your sending IP is on a blocklist that GMX manages itself, so its servers refuse the connection. GMX keeps a strict no tolerance policy toward spam.GMX, WEB.DEPermanent

Further reading

All 17 IONOS codesEvery code in the wikiPaste your own bounce

Beat · paid monitoring

A heartbeat for your email.

Beat runs every check on this site on a schedule: 41 checks, 33 blacklists and real inbox placement. The moment something breaks, it tells you what broke, why it matters, and the exact fix.

example.comWatching
  • SPFpass
  • DKIMpass
  • DMARCp=none
  • Blacklists0 of 33

Illustrative. Your domain, every few hours.

Also from us:Pulse: your own sending infrastructureConsulting: $65/hr, no retainer