SurfaceMap › i › ivillage.com

ivillage.com

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

Domain & DNS

fail

23 passed 4 warn 1 failed

Areas

iRegistration !Delegation ✗Nameservers ✓SOA !DNSSEC !Records

Problems

  • ✗
    Nameservers not responding
    Nameservers · These addresses did not answer, so resolvers waste time on timeouts: ns1.today.com (50.204.7.243): read udp 46.225.38.91:57119->50.204.7.243:53: i/o timeout; ns2.today.com (50.204.7.253): read udp 46.225.38.91:41622->50.204.7.253:53: i/o timeout.
    #14
  • !
    No IPv6
    Delegation · None of the nameservers has an IPv6 address, so IPv6-only resolvers can't reach them.
    #13
  • !
    Software version disclosed
    Nameservers · These nameservers report their software version via version.bind/version.server, which helps attackers find known vulnerabilities: nsa1.today.com: "9.18.28"; nsa2.today.com: "9.18.28". Hide or replace the version string.
    #17
  • !
    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
  • !
    Very low TTLs
    Records · These records have a TTL below 5m, causing extra queries and slower lookups: A (30s), MX (1m39s), NS (1m39s). Low TTLs are useful just before a planned change. The NS TTL at the parent is 2d and in the zone 1m39s; resolvers may use either.
    #32

Recent checks

✗

Full report

Domain & DNS report for ivillage.com ›

Mail

fail

13 passed 5 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
  • ✗
    Syntax errors
    SPF · Receivers reject the whole SPF record (permerror) because of: unknown mechanism "4:209.81.86.64/26".
    #25
  • !
    No key under common selectors
    DKIM · The _domainkey name exists but no DKIM key was found under the common selectors. Selectors are provider-specific; check yours with -selector.
    #7
  • !
    Not enabled
    DNSSEC · DNSSEC is not enabled for this domain. Consider enabling DNSSEC to protect against DNS spoofing attacks.
    #8
  • !
    Hosts without IP addresses
    MX · The following MX hosts could not be resolved to IP addresses: ivillage.com.s7a1.psmtp.com, ivillage.com.s7a2.psmtp.com, ivillage.com.s7b1.psmtp.com, ivillage.com.s7b2.psmtp.com
    #10
  • !
    Hosts without IPv6
    MX · The following MX hosts could not be resolved to IPv6 addresses: ivillage.com.s7a1.psmtp.com, ivillage.com.s7a2.psmtp.com, ivillage.com.s7b1.psmtp.com, ivillage.com.s7b2.psmtp.com
    #11
  • !
    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 ivillage.com ›