{
  "environment": {
    "user_agent": "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/155.0.0.0 Safari/537.36",
    "platform": "MacIntel",
    "device_pixel_ratio": 2,
    "date_utc": "2026-10-25T00:06:49.893Z",
    "user_agent_data": {
      "architecture": "arm",
      "brands": [
        {
          "brand": "Google Chrome",
          "version": "155"
        },
        {
          "brand": "Chromium",
          "version": "155"
        },
        {
          "brand": "Not(A:Brand",
          "version": "24"
        }
      ],
      "fullVersionList": [
        {
          "brand": "Google Chrome",
          "version": "155.0.8059.80"
        },
        {
          "brand": "Chromium",
          "version": "155.0.8059.80"
        },
        {
          "brand": "Not(A:Brand",
          "version": "24.0.0.0"
        }
      ],
      "mobile": false,
      "platform": "macOS",
      "platformVersion": "27.0.1"
    }
  },
  "local_date": "2026-10-24",
  "cases": [
    {
      "case_id": "browser",
      "record": {
        "recorded_utc": "2026-10-25T00:26:04.869Z",
        "component_path": "/demos/reference/url-warning-review-routes/",
        "title": "Reporting and warning-review routes",
        "text": "Reporting and warning-review routes\n\nDated 24 October 2026. This table describes checked sources; it does not scan a URL or tell you whether a site is safe. Unknown fields are preserved.\n\nFind a provider or phrase\nRoute category\nAll categories\nBrowser review\nEmail provider\nRegistrar\nHost or platform\nAnti-phishing\nReset\n\n3 of 20 rows\n\nReporting and warning-review routes — source-linked snapshot\nOrganization\tCategory\tPurpose\tRoute\tRequired information\tLimit\nGoogle Search Console\tbrowser warning review\tOwner requests review of security issues after correction.\tSearch Console Security Issues review\tIssue, correction and outcome explanation.\tDoes not establish a verdict from every browser or remove unrelated content.\nMicrosoft Defender SmartScreen\tbrowser warning review\tOwner challenges an incorrect SmartScreen site warning.\tWarning feedback and review email\tReported site and explanation through the documented warning-feedback route.\tA file submission portal is not substituted for a URL review.\nMozilla Firefox\tbrowser warning review\tOwner requests removal of an erroneous phishing-list entry.\tOfficial help links to Google removal form\tSite and explanation requested by the linked provider form; fields not audited.\tNot a separate independent blocklist or a universal warning appeal.\n\nAll rows are present in the HTML. Filtering uses this table only. Provider links open official guidance; no report is submitted here.\n\nJSON · Method · Source ledger",
        "active_element": {
          "tag": "BODY",
          "id": ""
        },
        "link_count": 23,
        "input_values": [
          {
            "id": "search",
            "value": ""
          },
          {
            "id": "filter",
            "value": "browser_warning_review"
          }
        ]
      }
    },
    {
      "case_id": "hosting",
      "record": {
        "recorded_utc": "2026-10-25T00:26:05.768Z",
        "component_path": "/demos/reference/url-warning-review-routes/",
        "title": "Reporting and warning-review routes",
        "text": "Reporting and warning-review routes\n\nDated 24 October 2026. This table describes checked sources; it does not scan a URL or tell you whether a site is safe. Unknown fields are preserved.\n\nFind a provider or phrase\nRoute category\nAll categories\nBrowser review\nEmail provider\nRegistrar\nHost or platform\nAnti-phishing\nReset\n\n5 of 20 rows\n\nReporting and warning-review routes — source-linked snapshot\nOrganization\tCategory\tPurpose\tRoute\tRequired information\tLimit\nAmazon Web Services\thosting platform\tReport abuse involving AWS resources.\tPublic form or Trust & Safety email\tSpecific URL and policy concern for content; technical incident reports require relevant logs and timestamps.\tNo guaranteed outcome or universal abuse-report API.\nCloudflare\thosting platform\tReport phishing involving a Cloudflare service.\tPublic form; entitled dashboard/API routes\tDomain and specific phishing URL; use appropriate complaint category.\tA CDN/proxy role does not prove Cloudflare hosts the origin content.\nGitHub\thosting platform\tReport abusive repositories, profiles or eligible content.\tRepository/user reporting and contact form\tRepository/user/content reference and explanation.\tNot a general website-warning appeal or a vulnerability-disclosure substitute.\nWordPress.com\thosting platform\tReport abusive content hosted by Automattic services.\tLogged-in report control or direct form\tRelevant hosted site/content and complaint details.\tDoes not cover every website running independently hosted WordPress software.\nDigitalOcean\thosting platform\tReport suspected abuse involving DigitalOcean infrastructure.\tSecurity Operations Center abuse form\tSelect abuse category; remaining required fields were not fully exposed.\tRead-only intake discovery does not confirm account requirements, handling time or resolution.\n\nAll rows are present in the HTML. Filtering uses this table only. Provider links open official guidance; no report is submitted here.\n\nJSON · Method · Source ledger",
        "active_element": {
          "tag": "BODY",
          "id": ""
        },
        "link_count": 23,
        "input_values": [
          {
            "id": "search",
            "value": ""
          },
          {
            "id": "filter",
            "value": "hosting_platform"
          }
        ]
      }
    },
    {
      "case_id": "porkbun",
      "record": {
        "recorded_utc": "2026-10-25T00:26:07.002Z",
        "component_path": "/demos/reference/url-warning-review-routes/",
        "title": "Reporting and warning-review routes",
        "text": "Reporting and warning-review routes\n\nDated 24 October 2026. This table describes checked sources; it does not scan a URL or tell you whether a site is safe. Unknown fields are preserved.\n\nFind a provider or phrase\nRoute category\nAll categories\nBrowser review\nEmail provider\nRegistrar\nHost or platform\nAnti-phishing\nReset\n\n1 of 20 rows\n\nReporting and warning-review routes — source-linked snapshot\nOrganization\tCategory\tPurpose\tRoute\tRequired information\tLimit\nPorkbun\tregistrar\tReport verifiable DNS abuse.\tAbuse intake and report-status route\tDefinitive, verifiable evidence; retain report ID.\tNot a general content, trademark or ownership-dispute arbiter.\n\nAll rows are present in the HTML. Filtering uses this table only. Provider links open official guidance; no report is submitted here.\n\nJSON · Method · Source ledger",
        "active_element": {
          "tag": "BODY",
          "id": ""
        },
        "link_count": 23,
        "input_values": [
          {
            "id": "search",
            "value": "Porkbun"
          },
          {
            "id": "filter",
            "value": ""
          }
        ]
      }
    },
    {
      "case_id": "none",
      "record": {
        "recorded_utc": "2026-10-25T00:26:07.565Z",
        "component_path": "/demos/reference/url-warning-review-routes/",
        "title": "Reporting and warning-review routes",
        "text": "Reporting and warning-review routes\n\nDated 24 October 2026. This table describes checked sources; it does not scan a URL or tell you whether a site is safe. Unknown fields are preserved.\n\nFind a provider or phrase\nRoute category\nAll categories\nBrowser review\nEmail provider\nRegistrar\nHost or platform\nAnti-phishing\nReset\n\n0 of 20 rows\n\nReporting and warning-review routes — source-linked snapshot\nOrganization\tCategory\tPurpose\tRoute\tRequired information\tLimit\n\nNo rows match. Clear a filter or use Reset.\n\nAll rows are present in the HTML. Filtering uses this table only. Provider links open official guidance; no report is submitted here.\n\nJSON · Method · Source ledger",
        "active_element": {
          "tag": "BODY",
          "id": ""
        },
        "link_count": 23,
        "input_values": [
          {
            "id": "search",
            "value": "zzzznevermatch"
          },
          {
            "id": "filter",
            "value": ""
          }
        ]
      }
    },
    {
      "case_id": "reset",
      "record": {
        "recorded_utc": "2026-10-25T00:26:08.317Z",
        "component_path": "/demos/reference/url-warning-review-routes/",
        "title": "Reporting and warning-review routes",
        "text": "Reporting and warning-review routes\n\nDated 24 October 2026. This table describes checked sources; it does not scan a URL or tell you whether a site is safe. Unknown fields are preserved.\n\nFind a provider or phrase\nRoute category\nAll categories\nBrowser review\nEmail provider\nRegistrar\nHost or platform\nAnti-phishing\nReset\n\n20 of 20 rows\n\nReporting and warning-review routes — source-linked snapshot\nOrganization\tCategory\tPurpose\tRoute\tRequired information\tLimit\nGoogle Search Console\tbrowser warning review\tOwner requests review of security issues after correction.\tSearch Console Security Issues review\tIssue, correction and outcome explanation.\tDoes not establish a verdict from every browser or remove unrelated content.\nMicrosoft Defender SmartScreen\tbrowser warning review\tOwner challenges an incorrect SmartScreen site warning.\tWarning feedback and review email\tReported site and explanation through the documented warning-feedback route.\tA file submission portal is not substituted for a URL review.\nMozilla Firefox\tbrowser warning review\tOwner requests removal of an erroneous phishing-list entry.\tOfficial help links to Google removal form\tSite and explanation requested by the linked provider form; fields not audited.\tNot a separate independent blocklist or a universal warning appeal.\nGmail\temail provider\tRecipient reports phishing or corrects a mistaken phishing label.\tMessage menu\tExisting message; choose the applicable reporting action.\tDoes not review a website for every browser or block every future sender.\nOutlook\temail provider\tRecipient reports a phishing message.\tMessage reporting control\tSelected suspicious message.\tReporting does not itself block the sender; blocking is separate.\nYahoo Mail\temail provider\tRecipient flags suspicious mail or Yahoo/AOL-origin abuse.\tSpam/report controls and abuse guidance\tSelected message and the relevant report control.\tFilter feedback is not a browser-warning appeal or guaranteed takedown.\nApple\temail provider\tReport email impersonating Apple.\tForward email to official reporting address\tSuspicious Apple-impersonation email.\tiCloud junk/abuse has separate handling; this is not a Safari URL appeal.\nNamecheap\tregistrar\tReport phishing associated with a registered domain or hosted content.\tSeparate registrar and hosting abuse addresses\tDomain, full URL, impersonated target and existing relevant evidence.\tRegistrar and hosting responsibility differ; one address does not establish both roles.\nGoDaddy\tregistrar\tReport phishing involving a GoDaddy-associated domain or service.\tPhishing abuse form\tContact email, impersonated brand, URL/domain and explanation; context fields also appear.\tAn intake/status interface does not promise action or browser-list removal.\nTucows Domains\tregistrar\tReport phishing/pharming involving the registrar family.\tDNS-abuse form linked from guidance\tRelevant domain and evidence; downstream form requirements not inspected.\tFamily coverage includes Ascio, Enom, EPAG and OpenSRS; unrelated hosts remain separate.\nPorkbun\tregistrar\tReport verifiable DNS abuse.\tAbuse intake and report-status route\tDefinitive, verifiable evidence; retain report ID.\tNot a general content, trademark or ownership-dispute arbiter.\nAmazon Web Services\thosting platform\tReport abuse involving AWS resources.\tPublic form or Trust & Safety email\tSpecific URL and policy concern for content; technical incident reports require relevant logs and timestamps.\tNo guaranteed outcome or universal abuse-report API.\nCloudflare\thosting platform\tReport phishing involving a Cloudflare service.\tPublic form; entitled dashboard/API routes\tDomain and specific phishing URL; use appropriate complaint category.\tA CDN/proxy role does not prove Cloudflare hosts the origin content.\nGitHub\thosting platform\tReport abusive repositories, profiles or eligible content.\tRepository/user reporting and contact form\tRepository/user/content reference and explanation.\tNot a general website-warning appeal or a vulnerability-disclosure substitute.\nWordPress.com\thosting platform\tReport abusive content hosted by Automattic services.\tLogged-in report control or direct form\tRelevant hosted site/content and complaint details.\tDoes not cover every website running independently hosted WordPress software.\nDigitalOcean\thosting platform\tReport suspected abuse involving DigitalOcean infrastructure.\tSecurity Operations Center abuse form\tSelect abuse category; remaining required fields were not fully exposed.\tRead-only intake discovery does not confirm account requirements, handling time or resolution.\nAnti-Phishing Working Group\tanti phishing\tContribute suspected phishing email to shared threat intelligence.\tEmail forwarding and linked reporting form\tFull phishing email, preferably forwarded as an attachment.\tA contribution is not a guaranteed personal response, refund or website takedown.\nNetcraft\tanti phishing\tReport suspicious URLs or phishing messages for investigation.\tPublic reporting entrypoint or forwarded email\tURL and existing context; suspicious email can be forwarded.\tProvider investigation is not a guaranteed takedown or removal from all browser lists.\nPhishTank\tanti phishing\tSubmit suspected phishing for community verification and sharing.\tRegistered website/email reporting routes\tSuspected phishing URL and supporting message information.\tCommunity classification does not control every warning system or guarantee removal.\nUK National Cyber Security Centre\tanti phishing\tReport a suspicious scam website.\tPublic report form\tURL, how it was received and optional explanatory context.\tNot an emergency service or a guarantee of removal; no suspicious link needs opening.\n\nAll rows are present in the HTML. Filtering uses this table only. Provider links open official guidance; no report is submitted here.\n\nJSON · Method · Source ledger",
        "active_element": {
          "tag": "BODY",
          "id": ""
        },
        "link_count": 23,
        "input_values": [
          {
            "id": "search",
            "value": ""
          },
          {
            "id": "filter",
            "value": ""
          }
        ]
      }
    }
  ],
  "network": {
    "schema": "resource-timing-action-log-v1",
    "component_path": "/demos/reference/url-warning-review-routes/",
    "start": {
      "utc": "2026-10-25T00:26:03.891Z",
      "time_ms": 332938.09999996424
    },
    "end": {
      "utc": "2026-10-25T00:26:08.619Z",
      "time_ms": 337666.09999996424
    },
    "baseline_resource_count": 0,
    "requests_during_window": 0,
    "requests": [],
    "csp_violations": [],
    "scope": "Resource Timing for the component document only; initial navigation excluded; not a packet capture, DNS log or browser-wide traffic capture."
  }
}
