nwsource.com

Checked 22 October 2026, 10:04 UTC · via 8.8.8.8
✗Problems found
19 passed 4 warnings 3 failed 3 info

SPF

pass

SPF record published

Found

Record
v=spf1 ip4:74.203.49.98 ip4:74.203.48.228 -all
DNS lookups
0 of 10
Void lookups
0 of 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.
  • ✓ 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

fail

p=none rua=mailto:dmarc_agg@vali.email (_dmarc.nwsource.com)

Found

Record
v=DMARC1; p=none rua=mailto:dmarc_agg@vali.email;
Found at
_dmarc.nwsource.com
TagValueMeaning
vDMARC1Version
pnone rua=mailto:dmarc_agg@vali.emailPolicy

Checks

  • ✗
    No valid policy
    No valid DMARC policy (p tag) was found. Ensure your DMARC record includes a valid p=reject, p=quarantine, or p=none tag.
    #4
  • ✓ Record published #5
    DMARC record exists for this domain.
  • ✗
    Invalid syntax
    DMARC record is invalid: invalid p value "none rua=mailto:dmarc_agg@vali.email".
    #17
  • ✓ Applies to 100% of mail #18
    DMARC policy applies to all failing mail.
  • !
    No aggregate reports (rua)
    DMARC record has no rua tag, so you receive no aggregate reports about who sends mail as your domain. Add rua=mailto:...
    #19
  • ✓ Subdomain policy: none rua=mailto:dmarc_agg@vali.email #20
    Subdomains are covered by policy 'none rua=mailto:dmarc_agg@vali.email'.

DKIM

fail

No keys found under the checked selectors

Found

Selectors
None found
_domainkey
NXDOMAIN

Checks

  • ✗
    No DKIM keys published
    _domainkey.nwsource.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

1 mail server

Found

PriorityHostRecordsReverse DNS
10nwsource-com.mail.protection.outlook.comA 52.101.8.5 A 52.101.8.32 A 52.101.202.159 A 52.101.8.71 AAAA 2a01:111:f403:c922::6 AAAA 2a01:111:f403:c946::14 AAAA 2a01:111:f403:c902::2 AAAA 2a01:111:f403:f805::2mail-dm2pr02cu00105.inbound.protection.outlook.com ✓ mail-dm8pr21cu00100.inbound.protection.outlook.com ✓ mail-ph5pr04cu00107.inbound.protection.outlook.com ✓ mail-dm2pr03cu00107.inbound.protection.outlook.com ✓ mail-bl2pr02cu00506.inbound.protection.outlook.com ✓ mail-ch3pr04cu00104.inbound.protection.outlook.com ✓ mail-sj0pr03cu01602.inbound.protection.outlook.com ✓ mail-co2pr03cu00202.inbound.protection.outlook.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.
  • ✓ All hosts have IPv6 #11
    All MX records resolve to IPv6 addresses.
  • !
    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 8 MX addresss 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
nwsource-com.mail.protection.outlook.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