Didn't find what you were looking for?


We have advanced search options to make it easier to locate posts, questions and answers on this community.
More information can be found at Advanced Search Options
If you are looking for something specific, please check if someone else has already asked or answered the same question.

A note regarding upgrades and Network Evolution:


Customers will be notified by their preferred communication method (email or text) when upgrades are available in their area
We expect 100% of our service area to be completed by end of next year

Security Shield false positive - jjellyfish.com blocked as "Suspicious Site"

csanford11
csanford11 Posts: 2 Novice

Subject: Security Shield false positive - jjellyfish.com blocked as "Suspicious Site"Our company website, jjellyfish.com (and www.jjellyfish.com), is being blocked by Spectrum Security Shield as a "Suspicious Site." This is a false positive.We are a U.S. B2B sales consulting firm; the site is our public marketing site with no user-generated content, no downloads, and no ad network.Block evidence from a Spectrum residential connection:- Port 80: HTTP 302 -> block.charter-prod.hosted.cujo.io/warn.html ("Suspicious Site Blocked")- Port 443: a non-TLS response is injected mid-handshake, surfacing as ERR_SSL_PROTOCOL_ERROR in the browser and "wrong version number" in OpenSSL- The block is intermittent - the same browser succeeds and fails within the same hourThe block is keyed to our domain, not to our host's IP address. Connecting to the same Cloudflare edge IP (172.67.196.98) with different SNI values: SNI=www.jjellyfish.com -> blocked SNI=jjellyfish.com -> blocked SNI=cloudflare.com -> connects normally SNI=discord.com -> connects normallyNo other reputation source corroborates the block:- Google Safe Browsing reports no unsafe content for either hostname- Valid TLS certificate, served via Cloudflare - The site loads normally from every non-Spectrum network we testedLikely trigger: we migrated hosting on 2026-08-29, moving an established domain from Squarespace to Railway behind Cloudflare. We suspect the sudden change in hosting infrastructure was auto-flagged.Requesting review, recategorization as a legitimate Business/Consulting site,and removal from the Security Shield block list for both jjellyfish.com andwww.jjellyfish.com.

Answers

  • Melissa_G
    Melissa_G Posts: 388 ✅ Verified Employee Moderator
    edited 2:47PM

    Good morning,

    The link below will allow for you to enter the website information and submit a request for the security shield to remove the block from your site.

    https://www.spectrum.net/support/internet/how-unblock-website-security-shield

  • csanford11
    csanford11 Posts: 2 Novice

    Thanks Melissa. That is the path we already took, and it is what brought us
    here.

    We submitted through that exact form. It was denied at 7:08AM this morning,
    unblock request ID 104739814: "We have reviewed and denied your request to
    unblock jjellyfish.com. We found this website to contain potentially harmful
    content." The denial came back in about an hour, and that form has a single URL
    field with no way to attach any evidence, so none of the following was ever
    looked at. Resubmitting it will just produce the same automated response with a
    new ID.

    Asking for this to be escalated to CUJO AI directly, and for a specific answer
    on what was actually detected.

    The block is keyed to our domain, not our host's IP address. Connecting to the
    same Cloudflare edge IP (172.67.196.98) with different SNI values:
    SNI=www.jjellyfish.com -> blocked SNI=cloudflare.com -> connects normally
    SNI=jjellyfish.com -> blocked SNI=discord.com -> connects normally
    Every subdomain is affected too, so this is a domain-level reputation flag, not
    anything specific to a page or piece of content.

    Nothing else corroborates it. Google Safe Browsing reports no unsafe content for
    either hostname, every flag false. The site serves normally from every
    non-Spectrum network we have tested, with valid TLS and no 5xx errors in our
    origin logs.

    After the denial we audited the entire domain rather than just refiling. We
    found and removed one orphaned DNS record, and added robots.txt and
    X-Robots-Tag: noindex to an internal tool on a subdomain. We also verified that
    tool enforces authentication server-side, with all data routes returning 401 to
    unauthenticated requests. We found nothing that would constitute harmful
    content.

    For context on the likely trigger: on 2026-08-29 we migrated this established
    domain to new hosting infrastructure. We suspect that change was auto-flagged.

    Requesting recategorization as a legitimate Business/Consulting site and removal
    from the Security Shield block list for jjellyfish.com, www.jjellyfish.com, and
    all subdomains.

  • James_M
    James_M Posts: 5,616 ✅ Verified Employee Moderator

    Hi @csanford11

    We are not the webhost for this domain. You would need to contact the webhost to investigate the error, then resubmit the request. The link provided is the most direct route to resolve the issue after errors are addressed. Alternately, Spectrum users can opt to disable Security Shield once they acknowledge any associated risk.