Support this IfPort check
IfPort gives the defensive outside answer first: which inbound TCP ports are visible on the public IP that made the request.
If that saved a deploy, firewall, VPN, proxy, CI, cloud, or incident-debugging loop, support keeps the same free check available for the next operator.
Support the commons
This donation action supports the free request-source-only outside check. Run a scan first to get a per-result receipt link.
Ready-to-send pledge
This is a support pledge handoff, not payment confirmation. Pick an amount, keep the note, and wire a real payment provider behind SUPPORT_LINK_PRIMARY when ready.
# IfPort support pledge
This is a support pledge handoff, not payment confirmation.
- Pledge intent: $5/mo
- Stable donate action: https://ifport.io/donate?pledge_usd=5&source=direct_donate_action
- Provider status: provider_missing
- Monthly target: $15/mo
- Current covered amount: $0/mo
- Current gap: $15/mo
- Nearest unlock: edge_trust_hardening ($15/mo gap)
- Operator outcome: A cleaner answer to the question: did IfPort scan my real public path or a proxy/VPN/sandbox hop?
- Receipt context: none
- Snapshot context: none
- Source: direct_donate_action
Safety boundary: request-source IP only; no arbitrary targets; no CIDR sweeps; no exploitation, payload delivery, or credential attacks.
Access note: support funds the public defensive commons and does not buy privileged scan access. The basic request-source answer stays free.
Nearest funded outcome
edge_trust_hardening needs $15/mo.
A cleaner answer to the question: did IfPort scan my real public path or a proxy/VPN/sandbox hop?
- 3 supporters at $5/mo close a $15/mo gap.
- 2 supporters at $10/mo close a $15/mo gap.
- 1 sponsor at $25/mo close a $15/mo gap.
Why support
Support funds hosting, TLS, worker capacity, abuse controls, monitoring, signed evidence, and remediation packs. It does not buy privileged scan access.
- Free request-source check stays free.
- No arbitrary targets become available through payment.
- No paid change to scan speed, scan scope, rate limits, or target permissions.
Support intent
Support ifport.io: fund edge_trust_hardening ($15/mo gap)
Status: provider_pending. Action: Record support intent and configure payment provider.
# IfPort support intent
I want to support ifport.io because it gives a free defensive outside check for inbound TCP exposure from the current request path.
- Stable donate action: https://ifport.io/donate
- Provider status: provider_missing
- Monthly target: $15/mo
- Current covered amount: $0/mo
- Current gap: $15/mo
- Nearest unlock: edge_trust_hardening ($15/mo gap)
- Operator outcome: A cleaner answer to the question: did IfPort scan my real public path or a proxy/VPN/sandbox hop?
Safety boundary: request-source IP only; no arbitrary targets; no CIDR sweeps; no exploitation, payload delivery, or credential attacks.
Access note: support funds the public defensive commons and does not buy privileged scan access. The basic request-source answer stays free.
Live proof
- Runtime scans observed: 247
- Action-required decisions: 56
- Endpoint 5xx total: 0
- Endpoint 429 total: 0
Provider links
- Payment provider is not configured yet. This page preserves the support intent and provider setup contract until `SUPPORT_LINK_PRIMARY` is deployed.
Provider setup status is visible at /readiness. Machine-readable donation context is available with /donate?format=json.