moroccoworldnews.com

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

SPF

fail

SPF record published

Found

Record
v=spf1 +ip4:69.164.204.207 ~all
DNS lookups
0 of 10
Void lookups
0 of 2
Records published
2

Checks

  • ✓ No deprecated ptr mechanism #1
    No ptr mechanism found in SPF record.
  • ✓ 0 of 10 DNS lookups #2
    SPF record needs 0 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.
  • ✗
    Multiple SPF records
    Found 2 SPF records. Publishing more than one v=spf1 record causes a permerror; merge them into a single record.
    #16
  • ✓ 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

warn

p=reject (_dmarc.moroccoworldnews.com)

Found

Record
v=DMARC1; p=reject; sp=reject; adkim=s; aspf=s; rua=mailto:zakarialouqdyeme.mwn@gmail.com
Found at
_dmarc.moroccoworldnews.com
External report address
mailto:zakarialouqdyeme.mwn@gmail.com (not authorized)
TagValueMeaning
vDMARC1Version
prejectPolicy
sprejectSubdomain policy
ruamailto:zakarialouqdyeme.mwn@gmail.comAggregate report addresses
adkimsDKIM alignment (r = relaxed, s = strict)
aspfsSPF alignment (r = relaxed, s = strict)

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:zakarialouqdyeme.mwn@gmail.com
  • ✓ Subdomain policy: reject #20
    Subdomains are covered by policy 'reject'.
  • !
    Report address not authorized
    These report addresses are in another domain that has not agreed to receive your reports, so receivers will not send them: mailto:zakarialouqdyeme.mwn@gmail.com (needs moroccoworldnews.com._report._dmarc.gmail.com). Ask the report provider to publish the record, or check the address.
    #29

DKIM

pass

Selectors: default, dkim, mail, email, k1, selector1, selector2, google, zoho, mx, key, mta, pm, dkim-smtp, s1, s2

Found

Selectors
default, dkim, mail, email, k1, selector1, selector2, google, zoho, mx, key, mta, pm, dkim-smtp, s1, s2
_domainkey
NOERROR
SelectorKeyFlags
defaultRSA 2048 bits
dkimrevoked
mailrevoked
emailrevoked
k1revoked
selector1revoked
selector2revoked
googlerevoked
zohorevoked
mxrevoked
keyrevoked
mtarevoked
pmrevoked
dkim-smtprevoked
s1revoked
s2revoked

Checks

  • ✓ Keys found: default, dkim, mail, email, k1, selector1, selector2, google, zoho, mx, key, mta, pm, dkim-smtp, s1, s2 #7
    DKIM keys found for this domain with selectors: default, dkim, mail, email, k1, selector1, selector2, google, zoho, mx, key, mta, pm, dkim-smtp, s1, s2
  • ✓ Strong keys #23
    DKIM keys are strong enough: default: RSA 2048 bits.
  • ✓ No problematic flags #24
    No test mode or SHA-1-only keys. Revoked keys (empty p=), which is fine after a key rotation: dkim, mail, email, k1, selector1, selector2, google, zoho, mx, key, mta, pm, dkim-smtp, s1, s2.

DNSSEC

warn

Signed, but no DS at parent

Found

DNSKEY records
Yes (2)
DS at parent
No
Algorithms
ECDSAP256SHA256 (13)
Key tags
2371, 34505
Signatures valid until
18 December 2026, 15:03 UTC

Checks

  • !
    Signed, but no DS at parent
    The zone is signed (DNSKEY present) but the parent has no DS record, so the chain of trust is incomplete. Publish the DS record at your registrar.
    #8
  • ✓ Signatures valid until 2026-12-18 #21
    DNSKEY signatures are valid until 2026-12-18T15:03:54Z.

MX

warn

1 mail server

Found

PriorityHostRecordsReverse DNS
0node6.myfcloudtx.comA 69.164.204.20769-164-204-207.ip.linodeusercontent.com ✓

Checks

  • ✓ 1 MX record #9
    Found 1 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: node6.myfcloudtx.com
    #11
  • !
    Single MX host, no backup
    Only one MX record found. For better email reliability, consider adding at least one backup MX server.
    #12
  • ✓ At most 5 MX records #13
    Found 1 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 1 MX address have a PTR record that resolves back to them.

TLS

warn

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

Found

DANE (TLSA records)

MX hostTLSADNSSEC
node6.myfcloudtx.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