Intel Basics

EVE Online D-Scan Guide

Field Summary

D-scan is most useful when it is treated as a repeated habit instead of a one-time check. WarpIntel reads pasted scan text as evidence, then separates visible ships, likely roles, missing context, and conservative next actions.

Last reviewed2026-06-14Data classPublic / user-enteredPrivate scopesNoneGameplay actionAdvisory only
Open Intel Desk

Checklist

  • Scan before warp, after landing, and before committing to a site or grid.
  • Compare visible ships with local count, recent kills, and known bait patterns.
  • Separate tackle, logistics, ewar, cyno, and high-damage hulls from ordinary travel traffic.
  • Write down what is missing: range, combat probes, on-grid names, and whether the hostile group is split.

Warning Signals

  • Combat probes appear near a PvE or mining ship.
  • Tackle ships appear with logistics or command destroyers.
  • A quiet system suddenly shows ships that do not match the site type.
  • The scan shows only bait-sized ships while local suggests a larger group.

Common Mistakes

  • Assuming no D-scan result means no danger.
  • Treating ship names as proof of pilot intent.
  • Ignoring scan range and angle when reporting intel.
  • Waiting for certainty instead of acting on stacked risk signals.

Next Actions

  • Paste the scan into Intel Desk and ask for likely roles.
  • Check the system risk page before moving the next ship.
  • Use Route Scout if the next destination crosses lowsec, nullsec, or a known camp route.

Independence And Safety

WarpIntel is an independent third-party project. These guides are reviewed practical notes for public and user-entered information only. They do not automate EVE gameplay, control the EVE client, inspect packets, or move ISK, contracts, assets, or corporation resources.

All Guides