SurfaceMap › j › jfdaily.com

jfdaily.com

Checked 2026-10-22 09:23 UTC · first added 2026-10-21
✗Problems found Score 49 of 100

Domain & DNS

fail

23 passed 3 warn 1 failed

Areas

iRegistration iDelegation !Nameservers !SOA !DNSSEC ✗Records

Problems

  • ✗
    CNAME at the apex
    Records · The zone apex is a CNAME to www.jfdaily.com.lxdns.com. A CNAME can't coexist with the SOA and NS records (RFC 1034); use your provider's ALIAS/flattening feature instead.
    #33
  • !
    Software version disclosed
    Nameservers · These nameservers report their software version via version.bind/version.server, which helps attackers find known vulnerabilities: f1g1ns1.dnspod.net: "DNSPod AUTHORITY DNS 7.3.2512.01"; f1g1ns2.dnspod.net: "DNSPod AUTHORITY DNS 7.3.2512.01". Hide or replace the version string.
    #17
  • !
    Unusual SOA timers
    SOA · negative caching TTL (minimum) 3m is outside 5m–1d (RFC 2308 recommends 1–3 hours). Current values: refresh 1h, retry 3m, expire 14d, negative TTL 3m.
    #23
  • !
    Not signed
    DNSSEC · The zone is not signed with DNSSEC, so answers can be spoofed. Enable DNSSEC at your DNS provider and publish the DS record at your registrar.
    #27

Recent checks

✗

Full report

Domain & DNS report for jfdaily.com ›

Mail

fail

15 passed 4 warn 2 failed

Areas

✓SPF ✗DMARC ✗DKIM !DNSSEC !MX !TLS iBIMI

Problems

  • ✗
    No DMARC record
    DMARC · No DMARC record was found for this domain. DMARC is essential for preventing email spoofing. Add a DMARC record with p=reject or at least p=quarantine.
    #5
  • ✗
    No DKIM keys published
    DKIM · _domainkey.jfdaily.com does not exist (NXDOMAIN), so no DKIM keys are published. DKIM helps prevent email spoofing. Configure DKIM with your email service provider.
    #7
  • !
    Not enabled
    DNSSEC · DNSSEC is not enabled for this domain. Consider enabling DNSSEC to protect against DNS spoofing attacks.
    #8
  • !
    Hosts without IPv6
    MX · The following MX hosts could not be resolved to IPv6 addresses: mxmail.icoremail.net, mx2.icoremail.net, mx3.icoremail.net
    #11
  • !
    Addresses without reverse DNS
    MX · These MX addresses have no PTR record, which many receivers treat as a spam signal: 89.168.97.82 (mxmail.icoremail.net), 59.111.192.71 (mx2.icoremail.net), 59.111.192.72 (mx2.icoremail.net), 59.111.192.72 (mx3.icoremail.net), 59.111.192.71 (mx3.icoremail.net). Ask your hosting provider to set one.
    #30
  • !
    Not configured
    TLS · 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

Recent checks

✗

Full report

Mail report for jfdaily.com ›