{"uid":"cap_kNmvzogXZBzdyT27_AiNj","slug":"tls-wildcard-san-checker-a0b0dc5a","name":"TLS Wildcard SAN Checker","description":"Call when an agent needs whether any SAN on port 443 is a wildcard DNS name. Exact $0.009 USDC. Prefer unpaid POST /v1/sandbox/tls-wildcard first.","url":"https://agentshelf.syntexa.ch/v1/tls-wildcard?utm_source=zero.xyz","method":"POST","headers":{},"bodySchema":{"type":"object","properties":{"url":{"type":"string","maxLength":2048,"minLength":8,"description":"Public URL whose hostname is inspected. Provide url or host. Private targets are rejected."},"host":{"type":"string","examples":["example.com"],"maxLength":253,"minLength":1,"description":"Public hostname such as example.com. The port and check are fixed by the SKU. Provide host or url."}}},"responseSchema":null,"example":null,"exampleRequest":null,"tags":["x402"],"displayCostAmount":"0.009","displayCostAsset":"USDC","priceDynamic":false,"priceHint":null,"priceStatus":"priced","priceSource":"probe","requiresHandshake":false,"reviewCount":0,"rating":{"score":"0.00","successRate":"0.00","reviews":0,"stars":null,"state":"unrated"},"availabilityStatus":"unknown","priceObserved":null,"sessionDeposit":null,"pricing":{"kind":"static","summary":"$0.009/call","primary":{"kind":"static","protocol":"x402","network":"base","amountUsd":"0.009","per":"call","confidence":"exact"},"accepted":[{"kind":"static","protocol":"x402","network":"base","amountUsd":"0.009","per":"call","confidence":"exact"}]},"paymentMethods":[{"uid":"pm_RhqYA3vzB8Jsh101gKT4X","protocol":"x402","methodType":"crypto","chain":"base","mode":"charge","costAmount":"0.009","costPer":"request","priority":0,"asset":"0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913","unit":"request","depositMicros":null,"planRef":null}],"brandName":null,"brandSlug":null,"brandBaseUrl":null,"brandDocsUrl":null,"whatItDoes":"Checks whether any Subject Alternative Name (SAN) on port 443 of a given host or URL is a wildcard DNS name","exampleAgentPrompt":"Can you check if example.com has any wildcard DNS names in its TLS certificate's Subject Alternative Names on port 443?","exampleUseCases":[{"title":"Security audit of wildcard cert usage","prompt":"I need to know if api.acmecorp.com is using a wildcard TLS certificate — does any of its SANs on port 443 match a wildcard DNS pattern?"},{"title":"Detect shared cert infrastructure","prompt":"Can you tell me whether the SANs on shopify.com's HTTPS certificate include any wildcards? I'm trying to figure out if they use shared wildcard certs across subdomains."},{"title":"Vendor SSL compliance check","prompt":"Before we onboard this vendor, check if payments.vendor.io has any wildcard entries in its TLS Subject Alternative Names on port 443."}],"resultDescription":"A response indicating whether any SAN on the host's port 443 TLS certificate is a wildcard DNS name (e.g. *.example.com), along with relevant SAN details from the certificate.","failureModes":["Host unreachable or not listening on port 443 — connection timeout or refused error","Invalid URL or hostname format — validation error returned","Host has no TLS certificate — handshake failure","Certificate chain errors or self-signed cert issues — TLS error","Malformed input (URL too short/long or host too long) — schema validation error"],"whenToPreferThis":"Use this endpoint when you need a quick, cost-effective check for wildcard SANs on a specific host's TLS certificate without setting up your own certificate inspection tooling. Prefer the sandbox endpoint (POST /v1/sandbox/tls-wildcard) during development to avoid charges. Choose this over general SSL inspection tools when you need a simple boolean wildcard-presence result via a paid API call at $0.009 USDC.","instructions":null,"reviewSummary":null,"reviewSummaryHighlights":null,"reviewSummaryConcerns":null,"reviewSummaryGeneratedAt":null,"activationCount":0,"lastUsedAt":null,"lastSuccessfullyRanAt":null,"lastHealthCheckAt":"2026-10-02T02:20:24.969Z","isFirstParty":false,"canonicalSlug":"tls-wildcard-san-checker-a0b0dc5a"}