news24.com

Checked 22 October 2026, 10:02 UTC · via 8.8.8.8
!Passed with warnings
21 passed 9 warnings 0 failed 3 info

SPF

warn

SPF record published

Found

Record
v=spf1 ip4:104.17.250.6 ip4:104.17.251.6 ip6:2606:4700::6811:fa06 ip6:2606:4700::6811:fb06 ip4:69.63.146.128/26 ip4:69.63.158.32/28 ip4:68.169.14.0/24 ip4:154.0.13.104/29 ip4:69.63.148.88/30 ip4:69.63.148.92/31 ip4:69.63.148.94 ip4:69.63.149.149/32 ip4:69.63.149.150/31 ip4:69.63.149.152/29 ip4:69.63.149.160/30 ip4:69.63.149.164 ip4:69.63.159.119 ip4:69.63.159.92 ip4:69.63.159.128/31 ip4:154.0.15.96/28 ip4:41.193.66.194/31 ip4:41.193.66.196/30 ip4:41.193.66.200/29 ip4:41.193.66.208/28 ip4:41.193.66.224/28 ip4:41.193.66.240/30 ip4:41.193.66.244/32 ip4:102.219.93.0/24 ip4:40.92.0.0/15 ip4:40.107.0.0/16 ip4:52.100.0.0/15 ip4:52.102.0.0/16 ip4:52.103.0.0/17 ip4:104.47.0.0/17 ip6:2a01:111:f400::/48 ip6:2a01:111:f403::/49 ip6:2a01:111:f403:8000::/51 ip6:2a01:111:f403:c000::/51 ip6:2a01:111:f403:f000::/52 ip4:167.89.0.0/17 ip4:208.117.48.0/20 ip4:50.31.32.0/19 ip4:198.37.144.0/20 ip4:198.21.0.0/21 ip4:192.254.112.0/20 ip4:168.245.0.0/17 ip4:149.72.0.0/16 ip4:159.183.0.0/16 ip4:134.128.64.0/18 ip4:159.26.176.0/20 ip4:223.165.113.0/24 ip4:223.165.115.0/24 ip4:223.165.118.0/23 ip4:223.165.120.0/23 ip4:74.125.0.0/16 ip4:209.85.128.0/17 ip6:2001:4860:4864::/56 ip6:2404:6800:4864::/56 ip6:2607:f8b0:4864::/56 ip6:2800:3f0:4864::/56 ip6:2a00:1450:4864::/56 ip6:2c0f:fb50:4864::/56 ip4:175.41.215.51 ip4:18.157.243.190 ip4:64.79.155.192 ip4:64.79.155.193 ip4:64.79.155.205 ip4:44.238.220.251 ip4:52.28.63.81 ip4:18.236.40.242 ip4:44.236.56.93 ip4:54.213.20.246 ip4:18.216.232.154 ip4:34.215.104.144 ip4:136.179.50.206 ip4:35.161.32.253 ip4:52.58.216.183 ip4:3.70.123.177 ip4:207.218.90.122 ip4:64.79.155.206 ip4:35.167.93.243 ip4:3.129.120.190 ip4:18.156.89.250 ip4:52.59.143.3 ip4:152.111.194.0/24 ip4:152.111.195.102 ip4:152.111.195.103 ip4:197.80.198.14 ip4:197.80.198.15 ~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.
  • !
    Broad IP ranges
    These ranges authorize tens of thousands of addresses or more: ip4:40.92.0.0/15, ip4:52.100.0.0/15. Check that you really own and send from all of them.
    #27

DMARC

warn

p=quarantine (_dmarc.news24.com)

Found

Record
v=DMARC1; p=quarantine; sp=none; pct=100; adkim=r; aspf=r; rua=mailto:924171862097401a914a279e3f439a0d@dmarc-reports.cloudflare.net,mailto:dns-tech@media24.com
Found at
_dmarc.news24.com
External report address
mailto:924171862097401a914a279e3f439a0d@dmarc-reports.cloudflare.net (authorized)
External report address
mailto:dns-tech@media24.com (not authorized)
TagValueMeaning
vDMARC1Version
pquarantinePolicy
spnoneSubdomain policy
pct100Percentage of mail the policy applies to
ruamailto:924171862097401a914a279e3f439a0d@dmarc-reports.cloudflare.net,mailto:dns-tech@media24.comAggregate report addresses
adkimrDKIM alignment (r = relaxed, s = strict)
aspfrSPF alignment (r = relaxed, s = strict)

Checks

  • !
    Policy: quarantine
    DMARC policy is set to 'quarantine'. Consider upgrading to 'reject' for stronger protection once you've verified legitimate emails are passing authentication.
    #4
  • ✓ 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:924171862097401a914a279e3f439a0d@dmarc-reports.cloudflare.net, mailto:dns-tech@media24.com
  • !
    Subdomains unprotected (sp=none)
    DMARC subdomain policy is sp=none, so spoofed mail from subdomains is not blocked. Consider sp=quarantine or sp=reject.
    #20
  • !
    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:dns-tech@media24.com (needs news24.com._report._dmarc.media24.com). Ask the report provider to publish the record, or check the address.
    #29

DKIM

warn

Selectors: mail, selector1, s1, s2

Found

Selectors
mail, selector1, s1, s2
_domainkey
NOERROR
SelectorKeyFlags
mailRSA 1024 bitstest mode (t=y)
selector1RSA 2048 bits
s1RSA 2048 bits
s2RSA 2048 bits

Checks

  • ✓ Keys found: mail, selector1, s1, s2 #7
    DKIM keys found for this domain with selectors: mail, selector1, s1, s2
  • !
    1024-bit DKIM key
    1024-bit RSA keys are the minimum and are considered weak today: mail (1024 bits). Rotate to a 2048-bit key.
    #23
  • !
    Key in test mode
    These keys have t=y, so receivers treat DKIM failures as a test: mail. Remove t=y once DKIM works.
    #24

DNSSEC

warn

Signed, but no DS at parent

Found

DNSKEY records
Yes (2)
DS at parent
No
Algorithms
ECDSAP256SHA256 (13)
Key tags
34505, 2371
Signatures valid until
19 December 2026, 12:27 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-19 #21
    DNSKEY signatures are valid until 2026-12-19T12:27:24Z.

MX

warn

2 mail servers

Found

PriorityHostRecordsReverse DNS
0news24-com.mail.protection.outlook.comA 52.101.160.1 A 52.101.162.1 A 52.101.162.0 A 52.101.160.0mail-jn3p275cu00401.inbound.protection.outlook.com ✓ mail-ct2p275cu01101.inbound.protection.outlook.com ✓ mail-ct2p275cu01000.inbound.protection.outlook.com ✓ mail-jnyp275cu00200.inbound.protection.outlook.com ✓
1news24-com.mail.protection.outlook.comA 52.101.160.0 A 52.101.162.0 A 52.101.160.1 A 52.101.162.1mail-jnyp275cu00200.inbound.protection.outlook.com ✓ mail-ct2p275cu01000.inbound.protection.outlook.com ✓ mail-jn3p275cu00401.inbound.protection.outlook.com ✓ mail-ct2p275cu01101.inbound.protection.outlook.com ✓

Checks

  • ✓ 2 MX records #9
    Found 2 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: news24-com.mail.protection.outlook.com, news24-com.mail.protection.outlook.com
    #11
  • ✓ Redundant MX hosts #12
    Found 2 MX records, which provides redundancy for email delivery.
  • ✓ At most 5 MX records #13
    Found 2 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
news24-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