What to know about Fatal hit-and-run investigation underway in Pueblo, victim identified
A powerful search engine that organizes and provides access to vast information on the internet.
Claims checked50
Techniques found0
Topics0
Coverage spectrum
Coverage gap: Low Left coverage
Left0%
Center80%
Right20%
5 sources compared across this story cluster. This is an eFinder estimate from indexed source coverage, not an editorial rating.
What happened
A powerful search engine that organizes and provides access to vast information on the internet.
Why it matters
COMPASS This cookie is used to collect website statistics and track conversion rates and Google ad personalisation 2 days __Secure-OSID This cookie is used to collect website statistics and track conversion rates and Google ad personalisation 6 months…
Common ground
The use of this cookie depends on your browser settings and whether you have chosen to have location turned on for your browser.
Perspective signals
No major persuasion pattern has been attached yet, so the source, headline, and evidence should carry most of the weight for readers.
Follow-up questions
What concrete event or decision sits underneath the headline: Fatal hit-and-run investigation underway in Pueblo, victim identified?
What evidence would most clearly confirm or weaken the claim that FCNEC Cookie for Google Funding Choices API which allows for functionality specific to consent gathering for things like GDPR consent and CCPA opt-out. 13 months?
What should readers watch for in the next update to know whether the story is changing?
eFinder analyzed this article and checked 50 claims against available evidence, cross-references, web search, and Wikipedia. Here is what the fact-checking layer found.
schedulePending40
infoSingle Source10
schedule
Claim 1: “FCNEC Cookie for Google Funding Choices API which allows for functionality specific to consent gathering for things like GDPR consent and CCPA opt-out. 13 months”
PENDING
This claim was extracted as a checkable statement from the article. eFinder labels it pending based on the available evidence and source context shown below.
schedule
Claim 2: “_gcl_dc Used by Google AdSense for experimenting with advertisement efficiency across websites using their services. 3 months”
PENDING
This claim was extracted as a checkable statement from the article. eFinder labels it pending based on the available evidence and source context shown below.
schedule
Claim 3: “HSID Download certain Google Tools and save certain preferences, for example the number of search results per page or activation of the SafeSearch Filter. Adjusts the ads that appear in Google Search. 2 years”
PENDING
This claim was extracted as a checkable statement from the article. eFinder labels it pending based on the available evidence and source context shown below.
schedule
Claim 4: “SAPISID Download certain Google Tools and save certain preferences, for example the number of search results per page or activation of the SafeSearch Filter. Adjusts the ads that appear in Google Search. 2 years”
PENDING
This claim was extracted as a checkable statement from the article. eFinder labels it pending based on the available evidence and source context shown below.
schedule
Claim 5: “receive-cookie-deprecation This cookie ensures browers in an experiment group of the Chrome-facilitated testing period include the Sec-Cookie-Deprecation request header as soon as it becomes available. 180 days”
PENDING
This claim was extracted as a checkable statement from the article. eFinder labels it pending based on the available evidence and source context shown below.
schedule
Claim 6: “_dcid Collects information on user behaviour on multiple websites. This information is used in order to optimize the relevance of advertisement on the website. 400 days”
PENDING
This claim was extracted as a checkable statement from the article. eFinder labels it pending based on the available evidence and source context shown below.
info
Claim 7: “TAID This cookie is used to link your activity across devices if you've previously signed in to your Google Account on another device. 14 days”
SINGLE SOURCE
The claim is only supported by multiple entries from a single source ('Krdo').
Claim 8: “__Host-GAPS Used to sign in with Google account. 1 year”
PENDING
This claim was extracted as a checkable statement from the article. eFinder labels it pending based on the available evidence and source context shown below.
schedule
Claim 9: “APISID Download certain Google Tools and save certain preferences, for example the number of search results per page or activation of the SafeSearch Filter. Adjusts the ads that appear in Google Search. 2 years”
PENDING
This claim was extracted as a checkable statement from the article. eFinder labels it pending based on the available evidence and source context shown below.
schedule
Claim 10: “OTZ Aggregate analysis of website visitors 17 days”
PENDING
This claim was extracted as a checkable statement from the article. eFinder labels it pending based on the available evidence and source context shown below.
schedule
Claim 11: “SMSV Used to sign in with Google account. session”
PENDING
This claim was extracted as a checkable statement from the article. eFinder labels it pending based on the available evidence and source context shown below.
info
Claim 12: “__Secure-OSID This cookie is used to collect website statistics and track conversion rates and Google ad personalisation 6 months”
SINGLE SOURCE
All provided evidence comes from a single source ('Krdo'), failing the requirement for 2+ independent sources for 'corroborated'.
Claim 13: “FPGCLDC Used to help advertisers determine how many times users who click on their ads end up taking an action on their site 90 days”
PENDING
This claim was extracted as a checkable statement from the article. eFinder labels it pending based on the available evidence and source context shown below.
schedule
Claim 14: “_gcl_au Used by Google AdSense for experimenting with advertisement efficiency across websites using their services. 3 months”
PENDING
This claim was extracted as a checkable statement from the article. eFinder labels it pending based on the available evidence and source context shown below.
schedule
Claim 15: “SEARCH_SAMESITE SameSite prevents the browser from sending this cookie along with cross-site requests. session”
PENDING
This claim was extracted as a checkable statement from the article. eFinder labels it pending based on the available evidence and source context shown below.
schedule
Claim 16: “FCCDCF Cookie for Google Funding Choices API which allows for functionality specific to consent gathering for things like GDPR consent and CCPA opt-out. 13 months”
PENDING
This claim was extracted as a checkable statement from the article. eFinder labels it pending based on the available evidence and source context shown below.
schedule
Claim 17: “SID Download certain Google Tools and save certain preferences, for example the number of search results per page or activation of the SafeSearch Filter. Adjusts the ads that appear in Google Search. 2 years”
PENDING
This claim was extracted as a checkable statement from the article. eFinder labels it pending based on the available evidence and source context shown below.
schedule
Claim 18: “AdID Show Google ads on non-Google sites and personalize ads based on user settings 2 weeks”
PENDING
This claim was extracted as a checkable statement from the article. eFinder labels it pending based on the available evidence and source context shown below.
schedule
Claim 19: “SIDCC Download certain Google Tools and save certain preferences, for example the number of search results per page or activation of the SafeSearch Filter. Adjusts the ads that appear in Google Search. 2 years”
PENDING
This claim was extracted as a checkable statement from the article. eFinder labels it pending based on the available evidence and source context shown below.
schedule
Claim 20: “SNID This cookie is used to collect website statistics and track conversion rates and Google ad personalisation 6 months”
PENDING
This claim was extracted as a checkable statement from the article. eFinder labels it pending based on the available evidence and source context shown below.
schedule
Claim 21: “__Secure-ENID Used by Google to prevent fraudulent login attempts. This also contains a Google user ID which can be used for statistics and marketing purposes following a successful login 11 Months”
PENDING
This claim was extracted as a checkable statement from the article. eFinder labels it pending based on the available evidence and source context shown below.
schedule
Claim 22: “GCLB This cookie is used in context with load balancing - This optimizes the response rate between the visitor and the site, by distributing the traffic load on multiple network links or servers. Session”
PENDING
This claim was extracted as a checkable statement from the article. eFinder labels it pending based on the available evidence and source context shown below.
info
Claim 23: “G_AUTHUSER_H Google Authentication session”
SINGLE SOURCE
The claim is only supported by multiple entries from a single source ('Krdo').
Claim 24: “AID Download certain Google Tools and save certain preferences, for example the number of search results per page or activation of the SafeSearch Filter. Adjusts the ads that appear in Google Search. 1 year”
PENDING
This claim was extracted as a checkable statement from the article. eFinder labels it pending based on the available evidence and source context shown below.
schedule
Claim 25: “NID This cookies is used to collect website statistics and track conversion rates and Google ad personalisation 1 year”
PENDING
This claim was extracted as a checkable statement from the article. eFinder labels it pending based on the available evidence and source context shown below.
schedule
Claim 26: “Secure-YEC Serve a similar purpose for YouTube, including detecting and resolving problems 13 months”
PENDING
This claim was extracted as a checkable statement from the article. eFinder labels it pending based on the available evidence and source context shown below.
info
Claim 27: “UULE sends precise location information from your browser to Googles servers so that Google can show you results that are relevant to your location. 6 hours”
SINGLE SOURCE
The claim is only supported by multiple entries from a single source ('Krdo').
compare_arrows
cross reference
SUPPORTS
— UULE sends precise location information from your browser to Googles servers so that Google can show you results that are relevant to your location... 6 hours
https://krdo.com/news/2026/05/04/colorados-largest-birding-h…
compare_arrows
cross reference
SUPPORTS
— UULE sends precise location information from your browser to Googles servers so that Google can show you results that are relevant to your location. ... 6 hours
https://krdo.com/news/top-stories/2026/05/03/warm-on-monday-…
compare_arrows
cross reference
SUPPORTS
— UULE sends precise location information from your browser to Googles servers so that Google can show you results that are relevant to your location. The use of this cookie depends on your browser sett…
https://krdo.com/video/weather-video/2026/05/03/tracking-nic…
+ 2 more evidence sources
schedule
Claim 28: “SSID Download certain Google Tools and save certain preferences, for example the number of search results per page or activation of the SafeSearch Filter. Adjusts the ads that appear in Google Search. 2 years”
PENDING
This claim was extracted as a checkable statement from the article. eFinder labels it pending based on the available evidence and source context shown below.
schedule
Claim 29: “_Secure-YEC Used to detect spam, fraud, and abuse to protect advertisers and YouTube creators 13 months”
PENDING
This claim was extracted as a checkable statement from the article. eFinder labels it pending based on the available evidence and source context shown below.
schedule
Claim 30: “cookies_accepted This functionality cookie is simply to verify that you have allowed us to set cookies on your machine 1 year”
PENDING
This claim was extracted as a checkable statement from the article. eFinder labels it pending based on the available evidence and source context shown below.
schedule
Claim 31: “__Host-1PLSID Used to sign in with Google account. 1 year”
PENDING
This claim was extracted as a checkable statement from the article. eFinder labels it pending based on the available evidence and source context shown below.
schedule
Claim 32: “1P_JAR These cookies are set via embedded youtube-videos. They register anonymous statistical data on for example how many times the video is displayed and what settings are used for playback. 1 month”
PENDING
This claim was extracted as a checkable statement from the article. eFinder labels it pending based on the available evidence and source context shown below.
schedule
Claim 33: “A Google uses this cookies to make advertising more engaging to users and more valuable to publishers and advertisers 17 days”
PENDING
This claim was extracted as a checkable statement from the article. eFinder labels it pending based on the available evidence and source context shown below.
info
Claim 34: “LSID This cookie is used to collect website statistics and track conversion rates and Google ad personalisation 6 months”
SINGLE SOURCE
The claim is only supported by multiple entries from a single source ('Krdo').
Claim 35: “SOCS Stores a user's state regarding their cookies choices 13 months”
PENDING
This claim was extracted as a checkable statement from the article. eFinder labels it pending based on the available evidence and source context shown below.
schedule
Claim 36: “CGIC Improves search results delivery by autocompleting queries based on user input 6 months”
PENDING
This claim was extracted as a checkable statement from the article. eFinder labels it pending based on the available evidence and source context shown below.
info
Claim 37: “OSID This cookie is used to collect website statistics and track conversion rates and Google ad personalisation 6 months”
SINGLE SOURCE
The claim is only supported by multiple entries from a single source ('Krdo').
Claim 39: “DSID Identifies signed-in users on non-Google sites to respect ad personalization settings 2 weeks”
PENDING
This claim was extracted as a checkable statement from the article. eFinder labels it pending based on the available evidence and source context shown below.
schedule
Claim 40: “CONSENT Google cookie consent tracker 20 years”
PENDING
This claim was extracted as a checkable statement from the article. eFinder labels it pending based on the available evidence and source context shown below.
schedule
Claim 41: “gac Measure user activity and ad campaign performance for advertisers 90 days”
PENDING
This claim was extracted as a checkable statement from the article. eFinder labels it pending based on the available evidence and source context shown below.
schedule
Claim 42: “ACCOUNT_CHOOSER Used to sign in with Google account. session”
PENDING
This claim was extracted as a checkable statement from the article. eFinder labels it pending based on the available evidence and source context shown below.
info
Claim 43: “DV This cookies is used to collect website statistics and track conversion rates and Google ad personalisation 1 year”
SINGLE SOURCE
The claim is only supported by multiple entries from a single source ('Krdo').
Claim 44: “COMPASS This cookie is used to collect website statistics and track conversion rates and Google ad personalisation 2 days”
SINGLE SOURCE
While there are 5 cross-references, they all originate from the same source ('Krdo'), meaning there is only one independent organization reporting this specific cookie detail.
Claim 45: “LSOLH This cookie is for authentication with your Google account 1 year”
PENDING
This claim was extracted as a checkable statement from the article. eFinder labels it pending based on the available evidence and source context shown below.
schedule
Claim 46: “gcl Helps advertisers determine user actions on their site after clicking an ad 90 days”
PENDING
This claim was extracted as a checkable statement from the article. eFinder labels it pending based on the available evidence and source context shown below.
schedule
Claim 47: “GN_PREF This cookie is used to collect website statistics and track conversion rates and Google ad personalisation 1 year”
PENDING
This claim was extracted as a checkable statement from the article. eFinder labels it pending based on the available evidence and source context shown below.
schedule
Claim 48: “_Secure-ENID Remembers user preferences like language, search results per page, and SafeSearch settings 13 months”
PENDING
This claim was extracted as a checkable statement from the article. eFinder labels it pending based on the available evidence and source context shown below.
schedule
Claim 49: “django_language Cookie necessary for the use of the options and services of the website. 3 month”
PENDING
This claim was extracted as a checkable statement from the article. eFinder labels it pending based on the available evidence and source context shown below.
info
Claim 50: “__Host-3PLSID Used to sign in with Google account. 1 year”
SINGLE SOURCE
The claim is only supported by multiple entries from a single source ('Krdo').
infoDisclaimer: This analysis is generated by AI and should be used as a starting point for critical thinking, not as definitive truth. Claims are verified against publicly available sources. Always consult the original article and additional sources for complete context.