SurfaceMap › j › jigsy.com

jigsy.com

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

Domain & DNS

warn

24 passed 3 warn 0 failed

Areas

iRegistration !Delegation ✓Nameservers ✓SOA !DNSSEC iRecords

Problems

  • !
    Glue differs from the zone
    Delegation · The addresses at the parent (glue) differ from the addresses in the zone: ns1.jigsy.com (glue 38.88.83.96, zone 38.88.83.96, 2001:550:7204:0:2:0:1:11); ns2.jigsy.com (glue 38.88.83.97, zone 38.88.83.97, 2001:550:7204:0:2:0:1:12); ns3.jigsy.com (glue 38.88.83.96, zone 38.88.83.96, 2001:550:7204:0:2:0:1:13); ns4.jigsy.com (glue 38.88.83.97, zone 38.88.83.97, 2001:550:7204:0:2:0:1:14); ns5.jigsy.com (glue 38.88.83.96, zone 38.88.83.96, 2001:550:7204:0:2:0:1:15); ns6.jigsy.com (glue 38.88.83.96, 38.88.83.97, zone 38.88.83.97, 2001:550:7204:0:2:0:1:16); ns7.jigsy.com (glue 38.88.83.96, zone 38.88.83.96, 2001:550:7204:0:2:0:1:17); ns8.jigsy.com (glue 38.88.83.97, zone 38.88.83.97, 2001:550:7204:0:2:0:1:18). Update the glue at your registrar.
    #8
  • !
    Nameservers in one network
    Delegation · all IPv4 addresses are in 38.88.83.0/24; all IPv6 addresses are in 2001:550:7204::/48. A single network failure takes all nameservers down; RFC 2182 recommends topologically separate networks (anycast setups are an exception).
    #10
  • !
    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 jigsy.com ›

Mail

fail

20 passed 5 warn 1 failed

Areas

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

Problems

  • ✗
    Policy: none (monitoring only)
    DMARC · DMARC policy is set to 'none', which only monitors but doesn't protect against spoofing. Consider upgrading to 'quarantine' or ideally 'reject'.
    #4
  • !
    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: mail1.jigsy.com, mail2.jigsy.com
    #11
  • !
    No aggregate reports (rua)
    DMARC · DMARC record has no rua tag, so you receive no aggregate reports about who sends mail as your domain. Add rua=mailto:...
    #19
  • !
    1024-bit DKIM key
    DKIM · 1024-bit RSA keys are the minimum and are considered weak today: dkim (1024 bits). Rotate to a 2048-bit key.
    #23
  • !
    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 jigsy.com ›