The application starts successfully and appears healthy (HTTP server responds, health endpoint returns ok), but performs zero actual monitoring. Every DNS lookup fails silently (error is logged but no notification sent), so no hostname state is ever populated, meaning port checks and TLS checks also never run.
This is the #1 blocker for 1.0 — the app literally does not do what it claims to do.
Fix
Implement all three services. The resolver should perform iterative DNS resolution from root servers (or at minimum use the system resolver). The port checker should do TCP connect. The TLS checker should do a TLS handshake with SNI and extract certificate info.
## Bug
All three core service implementations return `ErrNotImplemented`:
- `internal/resolver/resolver.go` — `LookupNS`, `LookupAllRecords`, `ResolveIPAddresses` all return `ErrNotImplemented`
- `internal/portcheck/portcheck.go` — `CheckPort` returns `ErrNotImplemented`
- `internal/tlscheck/tlscheck.go` — `CheckCertificate` returns `ErrNotImplemented`
## Impact
The application starts successfully and appears healthy (HTTP server responds, health endpoint returns ok), but performs zero actual monitoring. Every DNS lookup fails silently (error is logged but no notification sent), so no hostname state is ever populated, meaning port checks and TLS checks also never run.
This is the #1 blocker for 1.0 — the app literally does not do what it claims to do.
## Fix
Implement all three services. The resolver should perform iterative DNS resolution from root servers (or at minimum use the system resolver). The port checker should do TCP connect. The TLS checker should do a TLS handshake with SNI and extract certificate info.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Bug
All three core service implementations return
ErrNotImplemented:internal/resolver/resolver.go—LookupNS,LookupAllRecords,ResolveIPAddressesall returnErrNotImplementedinternal/portcheck/portcheck.go—CheckPortreturnsErrNotImplementedinternal/tlscheck/tlscheck.go—CheckCertificatereturnsErrNotImplementedImpact
The application starts successfully and appears healthy (HTTP server responds, health endpoint returns ok), but performs zero actual monitoring. Every DNS lookup fails silently (error is logged but no notification sent), so no hostname state is ever populated, meaning port checks and TLS checks also never run.
This is the #1 blocker for 1.0 — the app literally does not do what it claims to do.
Fix
Implement all three services. The resolver should perform iterative DNS resolution from root servers (or at minimum use the system resolver). The port checker should do TCP connect. The TLS checker should do a TLS handshake with SNI and extract certificate info.