Capabilities

We scan the same surface a threat actor would.

Our reviews are strictly non-invasive and limited to publicly reachable assets. We use passive discovery where possible and low-impact verification only within written scope. We never launch exploits, brute-force credentials, or disrupt operational traffic.

Perimeter Service Exposure

Detecting legacy protocols, unpatched service banners, and active ports that should never be facing the public internet. A database port open to the world, an ancient FTP server still answering requests, or a remote management interface visible outside the firewall are not theoretical findings. They are the first things an automated scanner picks up on any routine sweep.

We document every externally reachable service, identify its version and protocol, flag what is unnecessarily exposed, and give your IT team the specific firewall rules needed to close each one.

What we look for

  • Open database ports (MySQL, MSSQL, PostgreSQL) reachable from the public internet
  • Exposed remote desktop and remote management interfaces (RDP, VNC, SSH on non-standard ports)
  • Legacy file transfer services (FTP, Telnet) with version banners still active
  • Administrative web interfaces visible outside the network perimeter
  • Unintentionally exposed internal services identified through service banner analysis

Email Spoofing Vulnerabilities

Analyzing your active cryptographic mail headers (SPF, DKIM, and DMARC alignment) to block domain hijacking and phishing campaigns. A missing or misconfigured DMARC record means anyone can send an email that appears to come from your superintendent, your mayor, or your CFO. Your employees, parents, and constituents will have no technical way to tell it is fake.

We pull your full DNS mail configuration, check SPF record scope and validity, verify DKIM key publication, and verify DMARC policy publication and alignment posture. You get the exact DNS text records needed to close each gap.

What we look for

  • Missing or overly permissive SPF records that allow third-party spoofing
  • Absent or unenforced DMARC policy (p=none provides zero protection)
  • Missing DKIM key publication for active mail-sending domains
  • SPF/DMARC misalignment that breaks cryptographic verification
  • Parked or legacy domains without mail authentication that can still be spoofed

Cryptographic Protocol Decay

Identifying expired certificates, weak cipher suites, and broken SSL/TLS implementations that expose data in transit. An expired certificate on a public-facing login page does not just cause a browser warning. It is an active trust failure that signals to every visitor, and to every insurance underwriter scanning your domain, that your organization is not maintaining its systems.

We check certificate validity, expiration timelines, cipher suite strength, and TLS version support across all public-facing web properties. Findings include exact certificate details, expiration dates, and the specific configuration changes needed to pass modern security headers assessments.

What we look for

  • Expired or imminently expiring TLS certificates on public-facing services
  • Support for deprecated protocol versions (TLS 1.0, TLS 1.1, SSL 3.0)
  • Weak or export-grade cipher suites still accepted by the server
  • Missing HSTS headers that allow protocol downgrade attacks
  • Self-signed certificates on externally reachable services

Information Leakage

Scouring public code repositories and historical credential dumps to locate leaked organizational credentials before they are used for initial access. Developers push code to public GitHub repositories every day. Sometimes that code contains database connection strings, API keys, or administrative credentials that were never meant to leave the building. Threat actors run automated scanners against these repositories continuously.

We search public repositories, paste sites, and known breach databases for references to your organization's domains and systems. Any leaked credentials found are documented with source evidence so you can rotate them immediately.

What we look for

  • Organizational credentials appearing in known public breach datasets
  • API keys, connection strings, or secrets committed to public code repositories
  • Exposed configuration files containing authentication tokens
  • Internal system references visible in public code that reveal infrastructure details
  • Employee email addresses tied to reused passwords in breach databases