haveibeenpwned.uservoice.com/forums/275398-general/suggestions/49723205-include-last-seen-affected-date-in-stealer-resul

Preview meta tags from the haveibeenpwned.uservoice.com website.

Linked Hostnames

4

Thumbnail

Search Engine Appearance

Google

https://haveibeenpwned.uservoice.com/forums/275398-general/suggestions/49723205-include-last-seen-affected-date-in-stealer-resul

Include last seen / affected date in stealer results

As we are already aware (and have implemented) - it is not enough to know that an email appeared in stealer logs, the actual website credential was affected matters. This is surfaced through the v3 API from the email address, email domain, and website domain point of view, however much of this data is aggregated. This means that if an email address appears in multiple stealer logs it's not possible to know when it appeared for a given website domain. From an operator point of view this makes it difficult to know which end users are susceptible to *new* attacks from new stealer log entries (assuming that remediation action was taken). This could come from parsed log data (hard) or at a simplest level when it was last loaded / updated in HIBP (easy).



Bing

Include last seen / affected date in stealer results

https://haveibeenpwned.uservoice.com/forums/275398-general/suggestions/49723205-include-last-seen-affected-date-in-stealer-resul

As we are already aware (and have implemented) - it is not enough to know that an email appeared in stealer logs, the actual website credential was affected matters. This is surfaced through the v3 API from the email address, email domain, and website domain point of view, however much of this data is aggregated. This means that if an email address appears in multiple stealer logs it's not possible to know when it appeared for a given website domain. From an operator point of view this makes it difficult to know which end users are susceptible to *new* attacks from new stealer log entries (assuming that remediation action was taken). This could come from parsed log data (hard) or at a simplest level when it was last loaded / updated in HIBP (easy).



DuckDuckGo

https://haveibeenpwned.uservoice.com/forums/275398-general/suggestions/49723205-include-last-seen-affected-date-in-stealer-resul

Include last seen / affected date in stealer results

As we are already aware (and have implemented) - it is not enough to know that an email appeared in stealer logs, the actual website credential was affected matters. This is surfaced through the v3 API from the email address, email domain, and website domain point of view, however much of this data is aggregated. This means that if an email address appears in multiple stealer logs it's not possible to know when it appeared for a given website domain. From an operator point of view this makes it difficult to know which end users are susceptible to *new* attacks from new stealer log entries (assuming that remediation action was taken). This could come from parsed log data (hard) or at a simplest level when it was last loaded / updated in HIBP (easy).

  • General Meta Tags

    6
    • title
      Include last seen / affected date in stealer results – Customer feedback for Have I Been Pwned
    • X-UA-Compatible
      IE=Edge,chrome=1
    • charset
      utf-8
    • viewport
      width=device-width, initial-scale=1
    • csrf-param
      authenticity_token
  • Open Graph Meta Tags

    6
    • og:title
      Include last seen / affected date in stealer results
    • og:description
      As we are already aware (and have implemented) - it is not enough to know that an email appeared in stealer logs, the actual website credential was affected matters. This is surfaced through the v3 API from the email address, email domain, and website domain point of view, however much of this data is aggregated. This means that if an email address appears in multiple stealer logs it's not possible to know when it appeared for a given website domain. From an operator point of view this makes it difficult to know which end users are susceptible to *new* attacks from new stealer log entries (assuming that remediation action was taken). This could come from parsed log data (hard) or at a simplest level when it was last loaded / updated in HIBP (easy).
    • og:type
      article
    • og:url
      https://haveibeenpwned.uservoice.com/forums/275398-general/suggestions/49723205-include-last-seen-affected-date-in-stealer-resul
    • og:image
      https://s3.amazonaws.com/uploads.uservoice.com/logo/design_setting/252312/original/ShortLogo.png?1417092523
  • Link Tags

    5
    • alternate
      https://haveibeenpwned.uservoice.com/api/v1/oembed.json?url=https%3A%2F%2Fhaveibeenpwned.uservoice.com%2Fforums%2F275398-general%2Fsuggestions%2F49723205-include-last-seen-affected-date-in-stealer-resul
    • alternate
      https://haveibeenpwned.uservoice.com/api/v1/oembed.xml?url=https%3A%2F%2Fhaveibeenpwned.uservoice.com%2Fforums%2F275398-general%2Fsuggestions%2F49723205-include-last-seen-affected-date-in-stealer-resul
    • canonical
      https://haveibeenpwned.uservoice.com/forums/275398-general/suggestions/49723205-include-last-seen-affected-date-in-stealer-resul
    • stylesheet
      https://assets.uvcdn.com/pkg/clients/site2/index-9c56ab4a39505ec7480441b2f8a4d8746ea0edbab756a5f15907a9ffe7fbad4b.css
    • stylesheet
      /auth-component/uv-auth/uv-auth.css

Links

14