SurfaceMap › j › jal.com

jal.com

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

Domain & DNS

fail

25 passed 2 warn 1 failed

Areas

iRegistration ✓Delegation ✗Nameservers iSOA !DNSSEC iRecords

Problems

  • ✗
    No DNS over TCP
    Nameservers · DNS over TCP is required (RFC 7766); without it, large answers such as DNSSEC responses fail. Not answering over TCP: ns019-248anjmhlotnrdqt.2.d-53.jp (2001:240:bb81::29:1110): read tcp [2a01:4f8:1c1c:eebf::1]:51258->[2001:240:bb81::29:1110]:53: read: connection reset by peer; ns019-248anjmhlotnrdqt.2.d-53.org (2001:240:bb81::29:110): read tcp [2a01:4f8:1c1c:eebf::1]:60212->[2001:240:bb81::29:110]:53: read: connection reset by peer.
    #19
  • !
    Software version disclosed
    Nameservers · These nameservers report their software version via version.bind/version.server, which helps attackers find known vulnerabilities: ns019-248anjmhlotnrdqt.2.d-53.jp: "2026.10.8". 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

Recent checks

✗

Full report

Domain & DNS report for jal.com ›

Mail

fail

24 passed 2 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
  • !
    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 jal.com ›