Skip to content
emailrules.today

Authentication history · 60 days observed

away.com

Observed from 4 Aug 2026 to 3 Oct 2026. 1 dated move on record, newest first.

Where it stands today

Live lookup, 3 Oct 2026. The same check /check/away.com runs.

  • 1to fix
  • 2fine

  • Fix this

    No record

    This is the requirement no can meet for you, because it lives on your own . Microsoft rejects mail without it, and Gmail requires it above 5,000 a day.

    From DMARC p=none is monitoring, not enforcementSee what this looks like →

    This one needs you

    Publish v=DMARC1; p=none; =mailto: with an address somebody actually . At p=none it changes nothing about delivery, and it starts the reports you need before you could safely enforce anything.

  • Looks fine

    present, ending ~all

    Soft fail. Accepted everywhere, though -all is stronger once your sender list is complete.

    v=spf1 ip4:74.203.48.191 ip4:74.203.49.141 ip4:74.203.49.148 a mx ~all

    See what this looks like →

  • Looks fine

    keys published on 1 selector

    A key existing is not the same as working. Read a real received header and check the d= value matches your before you call this done.

    mail._domainkey (generic)

    From DKIM passing is not DKIM alignedSee what this looks like →

    Part platform, part you

    The key is your platform's to publish and it has. Whether it signs the domain in your is yours to confirm, and cannot show it — send one campaign to yourself and look for =pass header.d=away.com in the Authentication-Results header.

What has moved

One entry per day a published record actually changed. Days we looked and found nothing different are counted, not listed.

  1. MX hosts changed.

    was: away.com.s7a1.psmtp.com, away.com.s7a2.psmtp.com, away.com.s7b1.psmtp.com, away.com.s7b2.psmtp.com
now: (none)

  2. First observation — what was already published

    SPF published.

    v=spf1 ip4:74.203.48.191 ip4:74.203.49.141 ip4:74.203.49.148 a mx ~all

    No DMARC record.

    DKIM keys on selectors we probe.

    mail._domainkey (generic)

    MX records present.

    away.com.s7a1.psmtp.com, away.com.s7a2.psmtp.com, away.com.s7b1.psmtp.com, away.com.s7b2.psmtp.com
Where this comes from. Public DNS, and nothing else. We read the same TXT and MX records any mail server reads before accepting a message, on the days someone looked. There is no scan, no login, no mail, and no score here — only what was published and the date we saw it. Gaps are days we did not get a clean answer from a resolver, and we would rather leave those blank than guess at them.
Run the full checkSee which rules are yours