Suspect arrested following deadly hit-and-run in Pueblo

Krdo · May 22, 2026 · 1062 words · By Morris Richardson

headphones Listen to the eFinder podcast briefing

Generate a natural audio summary of this story

Daily briefing

What to know about Suspect arrested following deadly hit-and-run in Pueblo

A powerful search engine that organizes and provides access to vast information on the internet.

Claims checked 50

Techniques found 0

Topics 0

Coverage spectrum

Coverage gap: Low Left coverage

Left0%

Center86%

Right14%

7 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: Suspect arrested following deadly hit-and-run in Pueblo?
What evidence would most clearly confirm or weaken the claim that SEARCH_SAMESITE SameSite prevents the browser from sending this cookie along with cross-site requests?
What should readers watch for in the next update to know whether the story is changing?

open_in_new Read the original article: https://krdo.com/news/2026/05/22/suspect-arrested-following-deadly-hit-and-run-i…

fact_checkClaims Checked

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.

schedule Pending 40

info Single Source 10

schedule

Claim 1: “SEARCH_SAMESITE SameSite prevents the browser from sending this cookie along with cross-site requests.”

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 2: “LSID This cookie is used to collect website statistics and track conversion rates and Google ad personalisation 6 months”

SINGLE SOURCE

The information is provided solely by 'Krdo'.

compare_arrows

cross reference SUPPORTS — LSID This cookie is used to collect website statistics and track conversion rates and Google ad personalisation 6 months
https://krdo.com/news/top-stories/2026/05/06/fatal-hit-and-r…

compare_arrows

cross reference SUPPORTS — LSID This cookie is used to collect website statistics and track conversion rates and Google ad personalisation 6 months
https://krdo.com/news/2026/05/05/weather-alert-tracking-snow…

+ 2 more evidence sources

schedule

Claim 3: “_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 4: “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 5: “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 6: “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.

info

Claim 7: “UULE sends precise location information from your browser to Googles servers so that Google can show you results that are relevant to your location.”

SINGLE SOURCE

The evidence consists of multiple entries from the same source ('Krdo') without independent verification.

compare_arrows

cross reference SUPPORTS — sends precise location information from your browser to Googles servers so that Google can show you results that are relevant to your location
https://krdo.com/news/2026/04/10/greg-and-carrie-penner-dick…

compare_arrows

+ 2 more evidence sources

schedule

Claim 8: “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 9: “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.

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: “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 12: “G_AUTHUSER_H Google Authentication session”

SINGLE SOURCE

The claim is only supported by multiple entries from the same source ('Krdo').

compare_arrows

cross reference SUPPORTS — G_AUTHUSER_H Google Authentication session
https://krdo.com/news/2026/05/04/colorados-largest-birding-h…

compare_arrows

cross reference SUPPORTS — G_AUTHUSER_H Google Authentication session
https://krdo.com/news/2026/05/03/alleged-drunk-driver-injuri…

compare_arrows

cross reference SUPPORTS — G_AUTHUSER_H Google Authentication session
https://krdo.com/weather/local-forecast/2026/05/04/tracking-…

+ 2 more evidence sources

info

Claim 13: “g_enabled_idps Used for Google Single Sign On 1 year”

SINGLE SOURCE

The claim is supported only by entries from the same source ('Krdo').

compare_arrows

cross reference SUPPORTS — g_enabled_idps Used for Google Single Sign On 1 year
https://krdo.com/news/top-stories/2026/05/13/6th-street-down…

compare_arrows

cross reference SUPPORTS — g_enabled_idps Used for Google Single Sign On 1 year
https://krdo.com/news/2026/05/13/motorcycle-deaths-continue-…

compare_arrows

cross reference SUPPORTS — g_enabled_idps Used for Google Single Sign On 1 year
https://krdo.com/news/2026/05/06/garfield-county-train-derai…

+ 2 more evidence sources

schedule

Claim 14: “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 15: “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 16: “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.

schedule

Claim 17: “__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 18: “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 19: “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 20: “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 21: “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.

info

Claim 22: “TAID This cookie is used to link your activity across devices if you've previously signed in to your Google Account on another device.”

SINGLE SOURCE

The specific claim about the 'TAID' cookie is only found in the 'Krdo' cross-reference. The web search results are general Google Privacy and Account pages that do not specifically mention the 'TAID' cookie or its function.

travel_explore

web search NEUTRAL — When you sign in to your Google Account, you can see and manage your info, activity, security options, and privacy preferences to make Google work better for you. You can review and adjust some privac…
https://myaccount.google.com/

travel_explore

web search NEUTRAL — Use your Google Account. Email or phone.Not your computer? Use a private browsing window to sign in.
http://accounts.google.com/

travel_explore

web search NEUTRAL — Google apps, sites, and devices, like Search, YouTube, and Google Home. Platforms like the Chrome browser and Android operating system.
https://policies.google.com/privacy?hl=en

+ 1 more evidence source

schedule

Claim 23: “_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 24: “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.

schedule

Claim 25: “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 26: “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 27: “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 28: “__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 29: “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 30: “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 31: “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.

schedule

Claim 32: “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 33: “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'). There are no independent second sources to corroborate the claim.

compare_arrows

cross reference SUPPORTS — COMPASS This cookie is used to collect website statistics and track conversion rates and Google ad personalisation 2 days
https://krdo.com/news/top-stories/2026/05/03/warm-on-monday-…

compare_arrows

cross reference SUPPORTS — COMPASS This cookie is used to collect website statistics and track conversion rates and Google ad personalisation 2 days
https://krdo.com/news/2026/05/05/weather-alert-tracking-snow…

compare_arrows

+ 2 more evidence sources

info

Claim 34: “__Host-3PLSID Used to sign in with Google account. 1 year”

SINGLE SOURCE

The claim is reported only by 'Krdo'.

compare_arrows

cross reference SUPPORTS — __Host-3PLSID Used to sign in with Google account. 1 year
https://krdo.com/video/weather-video/2026/05/03/tracking-nic…

compare_arrows

cross reference SUPPORTS — __Host-3PLSID Used to sign in with Google account. 1 year
https://krdo.com/news/2026/05/04/csfd-responds-to-grass-fire…

compare_arrows

cross reference SUPPORTS — __Host-3PLSID Used to sign in with Google account. 1 year
https://krdo.com/news/2026/05/04/colorados-largest-birding-h…

+ 2 more evidence sources

schedule

Claim 35: “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 36: “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.

info

Claim 37: “OSID This cookie is used to collect website statistics and track conversion rates and Google ad personalisation 6 months”

SINGLE SOURCE

Only one source ('Krdo') provides this information across multiple entries.

compare_arrows

cross reference SUPPORTS — OSID This cookie is used to collect website statistics and track conversion rates and Google ad personalisation 6 months
https://krdo.com/news/top-stories/2026/05/03/warm-on-monday-…

compare_arrows

cross reference SUPPORTS — OSID This cookie is used to collect website statistics and track conversion rates and Google ad personalisation 6 months
https://krdo.com/news/2026/05/07/canon-city-high-school-ramp…

compare_arrows

+ 2 more evidence sources

schedule

Claim 38: “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.

schedule

Claim 39: “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 40: “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.

info

Claim 41: “__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'). No independent corroboration is available.

compare_arrows

cross reference SUPPORTS — __Secure-OSID This cookie is used to collect website statistics and track conversion rates and Google ad personalisation 6 months
https://krdo.com/news/top-stories/2026/05/06/fatal-hit-and-r…

compare_arrows

+ 2 more evidence sources

schedule

Claim 42: “_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 43: “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 44: “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 45: “_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.

schedule

Claim 46: “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 47: “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 48: “__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 49: “_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.

info

Claim 50: “DV This cookies is used to collect website statistics and track conversion rates and Google ad personalisation 1 year”

SINGLE SOURCE

Only one source ('Krdo') provides this information.

compare_arrows

cross reference SUPPORTS — DV This cookies is used to collect website statistics and track conversion rates and Google ad personalisation 1 year
https://krdo.com/news/top-stories/2026/05/06/fatal-hit-and-r…

compare_arrows

cross reference SUPPORTS — DV This cookies is used to collect website statistics and track conversion rates and Google ad personalisation 1 year
https://krdo.com/news/2026/05/05/weather-alert-tracking-snow…

+ 2 more evidence sources

info Disclaimer: 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.