hopin.com

Checked 22 October 2026, 09:12 UTC · via 8.8.8.8
✗Problems found
26 passed 2 warnings 1 failed 2 info

SPF

pass

SPF record published

Found

Record
v=spf1 include:%{i}._ip.%{h}._ehlo.%{d}._spf.vali.email ~all
DNS lookups
1 of 10
Void lookups
0 of 2

Checks

  • ✓ No deprecated ptr mechanism #1
    No ptr mechanism found in SPF record.
  • ✓ 1 of 10 DNS lookups #2
    SPF record needs 1 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.hopin.com)

Found

Record
v=DMARC1; p=reject; sp=reject; rua=mailto:dmarc_agg@vali.email,mailto:dmarc-report@hopin.com; ruf=mailto:dmarc-report@hopin.com; fo=1:s; rf=afrf
Found at
_dmarc.hopin.com
External report address
mailto:dmarc_agg@vali.email (authorized)
TagValueMeaning
vDMARC1Version
prejectPolicy
sprejectSubdomain policy
ruamailto:dmarc_agg@vali.email,mailto:dmarc-report@hopin.comAggregate report addresses
rufmailto:dmarc-report@hopin.comFailure report addresses
fo1:sFailure reporting options
rfafrfFailure report format

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_agg@vali.email, mailto:dmarc-report@hopin.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

warn

No keys found under the checked selectors

Found

Selectors
None found
_domainkey
NOERROR

Checks

  • !
    No key under common selectors
    The _domainkey name exists but no DKIM key was found under the common selectors. Selectors are provider-specific; check yours with -selector.
    #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

pass

5 mail servers

Found

PriorityHostRecordsReverse DNS
1aspmx.l.google.comA 142.251.127.26 AAAA 2a00:1450:4001:c21::1alcfrai-in-f26.1e100.net ✓ lcfrai-in-f26.1e100.net ✓
5alt1.aspmx.l.google.comA 142.250.147.27 AAAA 2a00:1450:4025:c01::1brd-in-f27.1e100.net ✓ rd-in-f27.1e100.net ✓
5alt2.aspmx.l.google.comA 172.253.152.26 AAAA 2a00:1450:4010:c22::1ayulpptr-in-f26.1e100.net ✓ yulpptr-in-f26.1e100.net ✓
10alt3.aspmx.l.google.comA 192.179.20.26 AAAA 2404:6800:4000:1027::1bncboms-in-f26.1e100.net ✓ ncboms-in-f27.1e100.net ✓
10alt4.aspmx.l.google.comA 192.178.158.26 AAAA 2404:6800:4013:813::1alcdels-in-f26.1e100.net ✓ lcdels-in-f26.1e100.net ✓

Checks

  • ✓ 5 MX records #9
    Found 5 MX records for this domain.
  • ✓ All hosts resolve #10
    All MX records resolve to valid IP addresses.
  • ✓ All hosts have IPv6 #11
    All MX records resolve to IPv6 addresses.
  • ✓ Redundant MX hosts #12
    Found 5 MX records, which provides redundancy for email delivery.
  • ✓ At most 5 MX records #13
    Found 5 MX records, which is within the recommended range (1-5).
  • ✓ 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 10 MX addresss have a PTR record that resolves back to them.

TLS

fail

MTA-STS record without policy · TLS-RPT · DANE on 0 of 5 MX hosts

Found

MTA-STS record
v=STSv1; id=20190425085700
Policy URL
https://mta-sts.hopin.com/.well-known/mta-sts.txt
Policy error
Get "https://mta-sts.hopin.com/.well-known/mta-sts.txt": tls: failed to verify certificate: x509: certificate is valid for *.storage.googleapis.com, *.googleapis.com, commondatastorage.googleapis.com, *.commondatastorage.googleapis.com, storage.googleapis.com, storage-p2.googleapis.com, *.storage-p2.googleapis.com, storage.mtls.googleapis.com, *.appspot.com.storage.googleapis.com, *.content-storage.googleapis.com, *.content-storage-p2.googleapis.com, *.content-storage-upload.googleapis.com, *.content-storage-download.googleapis.com, *.storage-upload.googleapis.com, *.storage-download.googleapis.com, not mta-sts.hopin.com
TLS-RPT record
v=TLSRPTv1; rua=mailto:tls-report@hopin.to

DANE (TLSA records)

MX hostTLSADNSSEC
aspmx.l.google.comnone-
alt1.aspmx.l.google.comnone-
alt2.aspmx.l.google.comnone-
alt3.aspmx.l.google.comnone-
alt4.aspmx.l.google.comnone-

Checks

  • ✓ Record published #32
    MTA-STS record found with id 20190425085700.
  • ✗
    Policy not reachable
    The MTA-STS record exists but the policy could not be fetched, so senders ignore MTA-STS: Get "https://mta-sts.hopin.com/.well-known/mta-sts.txt": tls: failed to verify certificate: x509: certificate is valid for *.storage.googleapis.com, *.googleapis.com, commondatastorage.googleapis.com, *.commondatastorage.googleapis.com, storage.googleapis.com, storage-p2.googleapis.com, *.storage-p2.googleapis.com, storage.mtls.googleapis.com, *.appspot.com.storage.googleapis.com, *.content-storage.googleapis.com, *.content-storage-p2.googleapis.com, *.content-storage-upload.googleapis.com, *.content-storage-download.googleapis.com, *.storage-upload.googleapis.com, *.storage-download.googleapis.com, not mta-sts.hopin.com.
    #33
  • ✓ Reports enabled #35
    TLS reports are sent to: mailto:tls-report@hopin.to
  • 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