schedulethreads.com

schedulethreads.com · Last checked 2026-10-04 17:40 UTC

schedulethreads.com

At risk, with 3 things to fix

schedulethreads.com scored 35/100 (grade F). The main issues are no SPF record and DMARC policy is none, plus 2 more. Detected senders: Google Workspace.

Checked 2026-10-04 17:40 UTC

1 passed2 need attention1 failing4 for informationDetected senders: Google Workspace
Fix this firstThe change with the biggest effect

Publish an SPF record

Lists the sending services detected for schedulethreads.com (Google Workspace) and rejects everything else. Add any other service that sends as schedulethreads.com before publishing. Changes: Added include:_spf.google.com for Google Workspace.

TypeTXT
Name / Host
schedulethreads.com

Some DNS providers want “@” here instead of the full domain.

Value
v=spf1 include:_spf.google.com -all

How to apply it

  1. Sign in where your domain’s DNS is managed. This is often where you bought the domain, such as Cloudflare, GoDaddy or Namecheap.
  2. Add a new TXT record with the name and value above.
  3. Save, then come back and re-check. DNS changes can take up to a few hours to show.

All checks

MXCan servers find your inbox?Only one MX hostInfo
  • Info: Only one MX host

    All mail for schedulethreads.com goes to smtp.google.com. Most hosted providers make that one name highly available; if you run your own server, consider a backup MX.

SPFWho may send as you?No SPF recordFailing
  • Fail: No SPF record

    schedulethreads.com publishes no TXT record starting with "v=spf1", so receivers cannot tell which servers may send mail for it. Publish one SPF record listing every service that sends as schedulethreads.com.

    How to fix this
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 schedulethreads.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 schedulethreads.com.

DMARCWhat happens to fakes?DMARC policy is noneNeeds attention
  • Warning: DMARC policy is none

    A none policy only monitors: mail that fails DMARC is still delivered, so anyone can spoof the domain. Once reports show your legitimate senders pass, move to quarantine and then reject.

    How to fix this
  • 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?No issues foundPass

Nothing to report.

BIMICan inboxes show your logo?No BIMI recordInfo
  • Info: No BIMI record

    No BIMI record at default._bimi.schedulethreads.com. BIMI is optional: it shows your logo next to your mail in supporting inboxes once DMARC is enforced.

    How to fix this
MTA-STSIs mail to you encrypted?No MTA-STS recordInfo
  • Info: No MTA-STS record

    No MTA-STS record at _mta-sts.schedulethreads.com. MTA-STS (RFC 8461) makes sending servers require TLS and a valid certificate when delivering to you, which blocks downgrade attacks.

    How to fix this
TLS-RPTWill you hear about failures?No TLS-RPT recordInfo
  • Info: No TLS-RPT record

    No TLS reporting record at _smtp._tls.schedulethreads.com. TLS-RPT (RFC 8460) tells senders where to send daily reports about failed encrypted deliveries to you.

    How to fix this

Other fixes

Strengthen the DMARC policyTXT

Quarantines 25% of mail that fails DMARC, a safe first step: check the reports for legitimate senders that fail before going further. There is no report address yet: set one up first (see the DMARC reporting fix) so you can confirm your legitimate mail passes before enforcing.

TypeTXT
Name / Host
_dmarc.schedulethreads.com

Some DNS providers want just “_dmarc” here.

Value
v=DMARC1; p=quarantine; pct=25; adkim=r; aspf=r
Replaces
v=DMARC1; p=none

Set up a DMARC report addressinstruction

Without a rua address nobody receives aggregate reports, so you cannot see who sends as schedulethreads.com or tell when it is safe to tighten the policy. Adding reporting does not change how receivers treat your mail.

Applies to: _dmarc.schedulethreads.com

  1. Get an address that collects DMARC aggregate reports: add schedulethreads.com to MailVakt to receive one, or sign up with any DMARC report service. 2. Edit the TXT record at _dmarc.schedulethreads.com and add rua=mailto:<that address>, keeping every other tag (p=none) as it is. 3. A report service on another domain must authorize schedulethreads.com; most publish that record for you.

Enable DKIM for Google Workspaceinstruction

Google Workspace generates the DKIM key for each account, so the exact record must come from Google Workspace. Without DKIM, mail it sends for schedulethreads.com cannot pass DMARC through DKIM.

Applies to: google._domainkey.schedulethreads.com

  1. In Google Workspace, enable DKIM signing for schedulethreads.com: Generate the key in Admin console > Apps > Gmail > Authenticate email, then publish the TXT record shown there. Publish exactly the record Google Workspace shows (TXT or CNAME) at the host name it gives, then turn signing on. Instructions: https://support.google.com/a/answer/174124

Publish the MTA-STS recordTXT

Tells sending servers that schedulethreads.com publishes an MTA-STS policy at https://mta-sts.schedulethreads.com/.well-known/mta-sts.txt. Change the id whenever the policy file changes.

TypeTXT
Name / Host
_mta-sts.schedulethreads.com

Some DNS providers want just “_mta-sts” here.

Value
v=STSv1; id=202610041740

Host the MTA-STS policy filepolicy-file

Serve this file over HTTPS with a valid certificate for mta-sts.schedulethreads.com. It lists your MX hosts and starts in testing mode; switch to mode: enforce once TLS-RPT reports show no failures.

Location
https://mta-sts.schedulethreads.com/.well-known/mta-sts.txt
Contents
version: STSv1
mode: testing
mx: smtp.google.com
max_age: 604800

Set up a TLS report addressinstruction

Sending servers will report TLS failures when delivering to schedulethreads.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.schedulethreads.com

  1. Pick an address that will receive TLS reports: a mailbox you read (for example tls-reports@schedulethreads.com, created first) or a TLS reporting service. 2. Publish a TXT record at _smtp._tls.schedulethreads.com with the value v=TLSRPTv1; rua=mailto:<that address>.

Prepare BIMIinstruction

BIMI shows your logo next to messages in supporting inboxes, but only for mail that passes DMARC under an enforced policy.

Applies to: default._bimi.schedulethreads.com

  1. Enforce DMARC first: p=quarantine or p=reject at 100% (no pct below 100). 2. Convert your logo to an SVG Tiny PS file and host it over HTTPS, for example https://schedulethreads.com/bimi/logo.svg. 3. For Gmail and Apple Mail, obtain a VMC or CMC certificate for the logo. 4. Publish a TXT record at default._bimi.schedulethreads.com with v=BIMI1, l= set to the logo URL and a= set to the certificate URL.