I’m getting reports of a category block for secure.bankofamerica.com from users in my ZTN tenant. Gateway shows the block reason is for ‘Hacking’ categorization (???). I tried reporting the issue via Radar Feedback (https://radar.cloudflare.com/domains/feedback/secure.bankofamerica.com), but I get a ’ TypeError r.data.result is undefined’ response.
1 Like
Worked around the issue via a DNS policy + domain list for this kind of situation. Bad Radar cat still exists (who approved that tag change?) & feedback page now shows ’ TypeError Cannot read properties of undefined (reading ‘filter’)'.
Hey,
Thanks for the report. Flagged for the team internally 
3 Likes
I also have the same issue.
I am using Zero Trust Gateway for home DNS and for the past 4 days I have been unable to use my bank of America online banking as the domain secure.bankofamerica.com is categorized as Questionable Content, Hacking category.
For now, I have created an explicit allow rule. Does anyone have the same problem?
It says TypeError
Cannot read properties of undefined (reading ‘filter’)
TypeError: Cannot read properties of undefined (reading ‘filter’)
I’m experiencing the same issue with 1.1.1.3 (1.1.1.1 for Families). When I try to log into my Bank of America account, secure.bankofamerica.com gets blocked.
Switching DNS to 1.1.1.1 resolves the issue, so I’m fairly confident it’s a problem with 1.1.1.3.
It started about 4-5 days ago. Prevents the user from logging into Bank of America’s online banking site.
Are you sure that’s the case, and it’s not some filtering/ad blocking you have on your end?
It looks fine for me
dig secure.bankofamerica.com @1.1.1.3 +short
secure.ecglb.bac.com.
171.159.118.200
Cloudflare Radar also shows no bad categories that would be blocking it
https://radar.cloudflare.com/domains/feedback/secure.bankofamerica.com
Edit: It looks like the CNAME Target is blocked actually
https://radar.cloudflare.com/domains/feedback/secure.ecglb.bac.com
But it still loads fine for me with 1.1.1.3 DoH, I get redirected probably, hmm.
I submitted feedback that the categorization is wrong. I assume on your end, when you properly login, it just fails / redirects you to secure.ecglb.bac.com?
Are you sure that’s the case, and it’s not some filtering/ad blocking you have on your end?
I can access it fine with 1.1.1.1, but when I switch to 1.1.1.3, it is blocked on all devices on my network.
Yep I see it now sorry, there’s no block on secure.bankofamerica.com but there is one on secure.ecglb.bac.com , which is the CNAME Target of it (and I assume also redirected to after or something). I forwarded this to CF and submitted categorization feedback for it on Radar, hopefully this is fixed soon.
1 Like
This is fixed now
secure.ecglb.bac.com, is no longer identified as a security threat, and 1.1.1.3 returns it correctly (which again matters because secure.bankofamerica.com is using it):
dig secure.ecglb.bac.com @family.cloudflare-dns.com +short
171.159.118.200
Not sure if it’s rolled out globally yet / there potentially may be some local DNS Cache on your devices, but if not, it should be soon.
2 Likes