megabus.com

Checked 22 October 2026, 09:44 UTC · via 8.8.8.8
✗Problems found
22 passed 4 warnings 1 failed 3 info

SPF

pass

SPF record published

Found

Record
v=spf1 mx a ip4:84.22.191.243 ip4:62.128.196.61 ip4:62.128.196.62 include:amazonses.com include:servers.mcsv.net ~all
DNS lookups
4 of 10
Void lookups
0 of 2

Checks

  • ✓ No deprecated ptr mechanism #1
    No ptr mechanism found in SPF record.
  • ✓ 4 of 10 DNS lookups #2
    SPF record needs 4 DNS lookups (limit is 10).
  • ✓ Ends with ~all #3
    SPF record properly uses ~all to restrict unauthorized senders.
  • ✓ Record published #6
    SPF record exists for this domain.
  • ✓ Single record #16
    Exactly one SPF record is published.
  • ✓ Valid syntax #25
    All SPF mechanisms and modifiers are valid.
  • ✓ No void lookups #26
    All include/redirect targets exist.
  • ✓ No overly broad IP ranges #27
    All ip4/ip6 ranges are narrow enough.

DMARC

pass

p=reject (_dmarc.megabus.com)

Found

Record
v=DMARC1; p=reject; fo=1; rua=mailto:dmarc_rua@emaildefense.proofpoint.com; ruf=mailto:dmarc_ruf@emaildefense.proofpoint.com
Found at
_dmarc.megabus.com
External report address
mailto:dmarc_rua@emaildefense.proofpoint.com (authorized)
External report address
mailto:dmarc_ruf@emaildefense.proofpoint.com (authorized)
TagValueMeaning
vDMARC1Version
prejectPolicy
ruamailto:dmarc_rua@emaildefense.proofpoint.comAggregate report addresses
rufmailto:dmarc_ruf@emaildefense.proofpoint.comFailure report addresses
fo1Failure reporting options

Checks

  • ✓ Policy: reject #4
    DMARC policy is set to 'reject', which provides the strongest protection against email spoofing.
  • ✓ Record published #5
    DMARC record exists for this domain.
  • ✓ Valid syntax #17
    DMARC record syntax is valid.
  • ✓ Applies to 100% of mail #18
    DMARC policy applies to all failing mail.
  • ✓ Aggregate reports enabled #19
    Aggregate reports are sent to: mailto:dmarc_rua@emaildefense.proofpoint.com
  • ✓ Subdomain policy: reject #20
    Subdomains are covered by policy 'reject'.
  • ✓ External report addresses authorized #29
    Report addresses in other domains have published their authorization.

DKIM

fail

No keys found under the checked selectors

Found

Selectors
None found
_domainkey
NXDOMAIN

Checks

  • ✗
    No DKIM keys published
    _domainkey.megabus.com does not exist (NXDOMAIN), so no DKIM keys are published. DKIM helps prevent email spoofing. Configure DKIM with your email service provider.
    #7

DNSSEC

warn

Not signed

Found

DNSKEY records
No (0)
DS at parent
No

Checks

  • !
    Not enabled
    DNSSEC is not enabled for this domain. Consider enabling DNSSEC to protect against DNS spoofing attacks.
    #8

MX

warn

9 mail servers

Found

PriorityHostRecordsReverse DNS
10smtp-in.iomartmail.comA 62.128.193.140smtp-in.iomartmail.com ✓
50mta1.iomartmail.comA 62.128.193.151mta1.iomartmail.com ✓
50mta2.iomartmail.comA 62.128.193.152mta2.iomartmail.com ✓
50mta3.iomartmail.comA 62.128.193.153mta3.iomartmail.com ✓
50mta4.iomartmail.comA 62.128.193.154mta4.iomartmail.com ✓
50mta5.iomartmail.comA 62.128.193.155mta5.iomartmail.com ✓
50mta6.iomartmail.comA 62.128.193.156mta6.iomartmail.com ✓
50mta7.iomartmail.comA 62.128.193.157mta7.iomartmail.com ✓
50mta8.iomartmail.comA 62.128.193.158mta8.iomartmail.com ✓

Checks

  • ✓ 9 MX records #9
    Found 9 MX records for this domain.
  • ✓ All hosts resolve #10
    All MX records resolve to valid IP addresses.
  • !
    Hosts without IPv6
    The following MX hosts could not be resolved to IPv6 addresses: smtp-in.iomartmail.com, mta1.iomartmail.com, mta2.iomartmail.com, mta3.iomartmail.com, mta4.iomartmail.com, mta5.iomartmail.com, mta6.iomartmail.com, mta7.iomartmail.com, mta8.iomartmail.com
    #11
  • ✓ Redundant MX hosts #12
    Found 9 MX records, which provides redundancy for email delivery.
  • !
    More than 5 MX records
    Found 9 MX records, which is more than the recommended maximum of 5. Too many MX records may indicate a misconfiguration.
    #13
  • ✓ No localhost targets #14
    No MX records pointing to localhost found.
  • ✓ No private IP addresses #15
    No MX records resolving to private IP addresses found.
  • ✓ No CNAME targets #22
    No MX records point to a CNAME.
  • ✓ Reverse DNS confirmed #30
    All 9 MX addresss have a PTR record that resolves back to them.

TLS

warn

no MTA-STS · no TLS-RPT · DANE on 0 of 9 MX hosts

Found

DANE (TLSA records)

MX hostTLSADNSSEC
smtp-in.iomartmail.comnone-
mta1.iomartmail.comnone-
mta2.iomartmail.comnone-
mta3.iomartmail.comnone-
mta4.iomartmail.comnone-
mta5.iomartmail.comnone-
mta6.iomartmail.comnone-
mta7.iomartmail.comnone-
mta8.iomartmail.comnone-

Checks

  • !
    Not configured
    MTA-STS is not configured, so other mail servers fall back to unencrypted delivery when TLS fails or is stripped by an attacker. Publish a _mta-sts TXT record and a policy at https://mta-sts.<domain>/.well-known/mta-sts.txt.
    #32
  • i
    Not configured
    TLS-RPT lets senders report TLS delivery problems to you. It is most useful together with MTA-STS or DANE.
    #35
  • i
    Not used
    No MX host publishes TLSA records. DANE lets senders verify your mail server's certificate through DNSSEC; it requires DNSSEC on the MX host's zone.
    #36

BIMI

info

No BIMI record

Checks

  • i
    Not configured
    BIMI shows your logo next to your mail in supporting mail clients. It requires DMARC enforcement.
    #38