TLS-RPT Report Parser

Store Positioning

Store title: TLS-RPT Report Parser

Short description: Audit tls-rpt report parser inputs and return structured findings, evidence rows, and a buyer-ready report for SEO, developer, and operations teams.

SEO title: TLS-RPT Report Parser — technical SEO, web, and domain audit

SEO description: Audit tls-rpt report parser inputs and return structured findings, evidence rows, and a buyer-ready report for SEO, developer, and operations teams. Use it to find crawlability, indexability, security, metadata, and page-quality issues with evidence-backed rows and audit reports.

Categories: DEVELOPER_TOOLS

Keywords: tls, rpt, report, parser, web/domain audit

Fixed-Inclusive PPE Pricing

This actor uses pay-per-event pricing. Event prices include Apify platform usage; users are not expected to pay a separate platform-usage pass-through charge for the configured pricing model.

• Tier: W1 — Web/domain audit
• Primary event: domain-audited at $0.00490 base
• Default max charge: $10.00
• Store discounts: FREE/BRONZE base, SILVER discounted, GOLD deepest approved discount

Event set:

• actor-start: base $0.00500, GOLD $0.00400. Tls Rpt Report Parser: charged when actor start is completed. The price includes Apify platform usage; no separate usage pass-through is intended.
• domain-audited: base $0.00490, GOLD $0.00392. Tls Rpt Report Parser: charged when domain audited is completed. The price includes Apify platform usage; no separate usage pass-through is intended.
• record-extracted: base $0.00372, GOLD $0.00298. Tls Rpt Report Parser: charged when record extracted is completed. The price includes Apify platform usage; no separate usage pass-through is intended.
• finding-emitted: base $0.00372, GOLD $0.00298. Tls Rpt Report Parser: charged when finding emitted is completed. The price includes Apify platform usage; no separate usage pass-through is intended.
• audit-report-generated: base $0.05000, GOLD $0.04000. Tls Rpt Report Parser: charged when audit report generated is completed. The price includes Apify platform usage; no separate usage pass-through is intended.

Public Task Concepts

• Audit public URLs for TLS-RPT Report Parser issues
• Find TLS-RPT Report Parser problems across a website
• Generate a technical TLS-RPT Report Parser report
• Audit tls issues across supplied public inputs
• Extract evidence-backed tls rows for client QA

What It Does

Audit tls-rpt report parser inputs and return structured findings, evidence rows, and a buyer-ready report for SEO, developer, and operations teams.

Audit tls-rpt report parser inputs and return structured findings, evidence rows, and a buyer-ready report for SEO, developer, and operations teams. Use it to find crawlability, indexability, security, metadata, and page-quality issues with evidence-backed rows and audit reports.

What It Does Not Do

• It does not bypass authentication, access private systems, or perform invasive security testing.
• It does not make unbounded crawls or unbounded external requests.
• It does not replace a full compliance, legal, or security assessment.
• It does not publish itself or change live Apify Store settings; release actions stay behind the repository scheduler and cloud replay gates.

Input Fields

• inputItems
• domains
• urls
• maxItems
• maxDomains
• timeoutMs
• includeReport
• includeSummary
• strictMode
• fixtureMode
• maxChargeUsd
• URLs

Example Input

{
  "maxItems": 5,
  "maxDomains": 5,
  "timeoutMs": 2500,
  "includeReport": true,
  "includeSummary": true,
  "strictMode": true,
  "maxChargeUsd": 1,
  "reports": [
    {
      "organizationName": "Example Mail",
      "dateRange": {
        "startDatetime": "2026-07-01T00:00:00Z",
        "endDatetime": "2026-07-02T00:00:00Z"
      },
      "policies": [
        {
          "policy": {
            "policyDomain": "example.com",
            "policyType": "sts"
          },
          "summary": {
            "totalSuccessfulSessionCount": 95,
            "totalFailureSessionCount": 5
          },
          "failureDetails": [
            {
              "resultType": "certificate-host-mismatch",
              "failedSessionCount": 5
            }
          ]
        }
      ]
    }
  ]
}

Output Fields

• reportId
• organizationName
• dateRangeStart
• dateRangeEnd
• policyType
• policyDomain
• resultType
• sendingMtaIp
• receivingMxHostname
• failureReasonCode
• failedSessionCount
• successfulSessionCount
• summary

Cost Controls

• Start with the tiny example input.
• Keep caps conservative: maxItems, maxDomains, timeoutMs, includeReport, includeSummary, maxChargeUsd.
• Keep pass-through usage set to OFF unless a future live cost review requires a change.
• Generate reports only when the report event is configured and budget allows it.

Public Task Examples

Audit public URLs for TLS-RPT Report Parser issues

• Search intent: audit public urls for tls-rpt report parser issues
• Expected output: Dataset rows and summary artifacts for TLS-RPT Report Parser.

Find TLS-RPT Report Parser problems across a website

• Search intent: find tls-rpt report parser problems across a website
• Expected output: Dataset rows and summary artifacts for TLS-RPT Report Parser.

Generate a technical TLS-RPT Report Parser report

• Search intent: generate a technical tls-rpt report parser report
• Expected output: Dataset rows and summary artifacts for TLS-RPT Report Parser.

Limitations

• Results depend on the supplied records, fixture data, or public DNS/HTTP signals available to the actor.
• Network and DNS results can differ by resolver, region, CDN, or runtime environment.
• Recommendations are operational guidance and should be reviewed before production changes.

FAQ

What should I run first?

Use the bundled tiny input or a single low-risk domain/record before expanding caps.

Does this actor require credentials?

No credentials are required for the default bounded workflow.

How is billing protected?

Paid dataset rows are emitted only after the configured PPE guard accepts the relevant event charge.