How the Security Check Works

No break-in attempts. No password guessing. I only read what your server already announces to the public internet — the same information a hacker can see from their desk.

What I Check · What I Never Do

Public-facing information only. I read what the open internet can already see — nothing private, nothing that requires a login.

What I Scan

Open ports on your domain (standard 15-port sweep — what services are publicly listening)
Service banners (the version information your software announces when a connection is made)
TLS/SSL certificate validity, expiry, and protocol versions (encrypted connection check)
HTTP security headers (HSTS, CSP, X-Frame-Options — browser protection controls)
DNS records (publicly resolvable subdomains and email security records)
Known software vulnerabilities matching the reported service versions (CVE database)

What I Don't Do

Authentication attempts (no password guessing, no credential stuffing)
Exploit attempts (I never try to use a vulnerability I find)
DoS / DDoS / brute force / aggressive scans
Data exfiltration (I never read DB contents, file contents, email contents)
Phishing of staff (I don’t email or call your team to test them)
Physical / social engineering tests

Tools Used

Industry-standard open-source security tooling — the same tools your auditors and threat-modellers use.

nmap with banner detection (-sV) — port + service identification
openssl s_client — TLS validation
curl with custom headers — HTTP response inspection
dig + crt.sh — DNS + certificate-transparency lookups
NVD CVE database (publicly licensed) for version → known-vuln mapping

Your 90-Day Window to Fix Before Anything Is Published

Every Titanos finding ships with a 90-day responsible disclosure window. If a recipient needs more time to remediate, I extend it. I do not publish, sell, or share findings with third parties during that window.

This is the same 90-day window followed by national security agencies (AustCERT, CERT NZ, CSA Singapore) and security researchers worldwide. It gives your business time to fix the issue before anyone else knows it exists.

Scope

I scan organisations across Australia, New Zealand, and Singapore — typically B2B SaaS, mid-market commercial, and listed companies. I do not scan:

Government domains (.gov.au, .gov.nz, .gov.sg, .govt.nz, .edu.au)
Critical infrastructure operators
Companies that have asked to be removed (suppression list honoured forever)
Domains that don’t resolve or have no public services

What You Get

The standard external scan output:

Findings ranked by severity (Critical, High, Medium, Low, Info)
For each finding: the evidence, the affected port/service, and a remediation step
For each finding: reproduction command (so your engineering team can verify independently)
Summary suitable for sharing with auditors, insurers, or your board

How I Deliver

Free protective disclosure: a plain-text report emailed direct to your inbox from kyle@titanos.tech within 2 business days. No signup. No portal to log into. Reply to the email if you need the findings in a different format for your auditor.

Beyond the free check, two paid engagements: Privacy Act Compliance (done with you) (done with you) and AI Implementation for Business (project-quoted). Both are listed at titanos.tech.

How to Verify Me

Three independent ways. Every claim I make is one of these checks away from a third-party audit.

Verify the ABN

Confirm 34 318 502 254 at abr.business.gov.au.

Verify with the same tool I used

Every finding ships with the exact nmap -sV {target} -p {port} command I ran. Copy it, run it yourself, and you will get the same result. Independently verifiable in 30 seconds.

Email Kyle directly

Email kyle@titanos.tech directly to confirm any communication is genuine. (This is the footer/about contact mention — not a scan request route. Use the form on /scan for that.)

Questions I get

Removal

Reply remove to any email from me and your domain is suppressed permanently. I honour the request immediately.