SurfaceMap › j › janssen.com

janssen.com

Checked 2026-10-22 09:23 UTC · first added 2026-10-21
!Passed with warnings Score 76 of 100

Domain & DNS

warn

24 passed 4 warn 0 failed

Areas

iRegistration !Delegation iNameservers !SOA !DNSSEC !Records

Problems

  • !
    Glue differs from the zone
    Delegation · The addresses at the parent (glue) differ from the addresses in the zone: ns01.jnjdns.com (glue 45.54.33.1, zone 45.54.33.1, 2607:f740:e659::1); ns02.jnjdns.com (glue 45.54.33.65, zone 45.54.33.65, 2607:f740:e659:4::1); ns03.jnjdns.com (glue 45.54.33.129, zone 45.54.33.129, 2607:f740:e659:8::1); ns04.jnjdns.com (glue 45.54.33.193, zone 45.54.33.193, 2607:f740:e659:c::1). Update the glue at your registrar.
    #8
  • !
    Unusual SOA timers
    SOA · retry 2h should be shorter than refresh 2h. Current values: refresh 2h, retry 2h, expire 30d, negative TTL 30m.
    #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
  • !
    Very low TTLs
    Records · These records have a TTL below 5m, causing extra queries and slower lookups: A (4m9s), AAAA (4m9s). Low TTLs are useful just before a planned change. The NS TTL at the parent is 2d and in the zone 1h; resolvers may use either.
    #32

Recent checks

!

Full report

Domain & DNS report for janssen.com ›

Mail

warn

23 passed 4 warn 0 failed

Areas

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

Problems

  • !
    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 IPv6
    MX · The following MX hosts could not be resolved to IPv6 addresses: mx1.jnj-sd.iphmx.com, mx2.jnj-sd.iphmx.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 janssen.com ›