wixsite.com
Poor, with 5 things to fix
wixsite.com scored 40/100 (grade D). The main issues are no MX records and no DKIM key found for the common selectors, plus 5 more.
Checked 2026-10-04 02:07 UTC · fresh check
Diagnosis notes
- Warning: DNS lookup budget exhausted
This diagnosis stopped sending DNS queries after 150 queries. Checks that needed more lookups report their remaining results as unknown; the domain's records may be unusually large or slow to answer.
Set up a DMARC report address
Without a rua address nobody receives aggregate reports, so you cannot see who sends as wixsite.com or tell when it is safe to tighten the policy. Adding reporting does not change how receivers treat your mail.
Applies to: _dmarc.wixsite.com
- Get an address that collects DMARC aggregate reports: add wixsite.com to MailVakt to receive one, or sign up with any DMARC report service. 2. Edit the TXT record at _dmarc.wixsite.com and add rua=mailto:<that address>, keeping every other tag (p=reject) as it is. 3. A report service on another domain must authorize wixsite.com; most publish that record for you.
All checks
MXCan servers find your inbox?No MX recordsFailing
- Fail: No MX records
wixsite.com has no MX records and no A/AAAA fallback, so it cannot receive mail, including bounces and DMARC reports. Publish an MX record pointing at your mail provider.
SPFWho may send as you?No issues foundPass
Nothing to report.
DKIMAre your emails signed?No DKIM key found for the common selectorsNeeds attention
- Warning: No DKIM key found for the common selectors
None of the 47 selectors probed under wixsite.com publish a DKIM key. DNS cannot list selectors, so a key under a custom selector may exist: find the s= value in the DKIM-Signature header of a message you sent and check that selector. If DKIM is not set up, enable it at each service that sends mail for wixsite.com.
- Warning: Some DKIM lookups failed
17 of 47 selector lookups under wixsite.com returned TIMEOUT, so whether those selectors hold a key is unknown. Try again later; if it persists, check the domain's nameservers.
DMARCWhat happens to fakes?No DMARC aggregate report addressNeeds attention
- Warning: No DMARC aggregate report address
Without a rua address you receive no aggregate reports, so you cannot see who sends as your domain or safely tighten the policy.
How to fix this
AlignmentDoes it match your From?SPF alignment is unknownInfo
- Info: SPF alignment is unknown
The SPF record of wixsite.com authorizes no sender (no +ip4, +ip6, +a, +mx, +exists or +ptr term, include of a record that has one, or +all before all), so SPF never passes and cannot align. That is correct for a domain that sends no mail; otherwise DMARC depends on DKIM alone.
BIMICan inboxes show your logo?Could not look up the BIMI recordNeeds attention
- Warning: Could not look up the BIMI record
The TXT query for default._bimi.wixsite.com returned TIMEOUT, so BIMI status is unknown. Try again later.
MTA-STSIs mail to you encrypted?Could not look up the MTA-STS recordNeeds attention
- Warning: Could not look up the MTA-STS record
The TXT query for _mta-sts.wixsite.com returned TIMEOUT, so MTA-STS status is unknown. Try again later.
TLS-RPTWill you hear about failures?No TLS-RPT recordInfo
- Info: No TLS-RPT record
No TLS reporting record at _smtp._tls.wixsite.com. TLS-RPT (RFC 8460) tells senders where to send daily reports about failed encrypted deliveries to you.
How to fix this
Other fixes
Set up a TLS report addressinstruction
Sending servers will report TLS failures when delivering to wixsite.com, which you need before enforcing MTA-STS. The address must accept TLS reports; a DMARC report address does not necessarily do so.
Applies to: _smtp._tls.wixsite.com
- Pick an address that will receive TLS reports: a mailbox you read (for example tls-reports@wixsite.com, created first) or a TLS reporting service. 2. Publish a TXT record at _smtp._tls.wixsite.com with the value v=TLSRPTv1; rua=mailto:<that address>.