dailysignal.com
Nov 22, 2022
A full WordPress MySQL database dump from The Daily Signal (dailysignal.com), the digital news outlet of The Heritage Foundation. The dump includes WordPress core tables covering users, comments, posts, metadata, options, redirections, Yoast SEO data, and Gravity Forms entries. The heartbeat table shows a last activity timestamp of 2022-11-22, suggesting the dump was taken around that date. The data exposes site user accounts, commenter email addresses and IPs, post content, and internal site configuration.
Data found in this dataset
Source files
Expand any file to inspect its column headers and the LLM's field-mapping reasoning, recorded during ingestion.
daily-signal_dev_database_new___pantheon_heartbeat.csv0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
Notes: This is a log file showing timestamp and actor (user/resurrection) only. No PII fields present. Columns are purely internal system logs and do not contain any personal information.
daily-signal_dev_database_new__attachment_ids.csv0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
Notes: This is a WordPress metadata table (wp_postmeta) showing post ID to thumbnail ID mappings. All columns are internal IDs (_thumbnail_id) and post identifiers with no PII content. No email addresses, names, addresses, or other personal data appear in any column.
daily-signal_dev_database_new__wp_commentmeta.csv0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
Notes: This is a WordPress metadata table (wp_commentmeta). All columns are internal metadata keys/values unrelated to PII. No PII fields present. The 'user' values in akismet_history are internal system accounts (bstewart), not external user identifiers.
daily-signal_dev_database_new__wp_comments.csv241,670 rows
File structure
Notes: Unstructured fallback: no PII columns mapped, but the raw text carries emails
daily-signal_dev_database_new__wp_links.csv0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
Notes: No PII columns detected. All columns are internal identifiers, URLs, categories, visibility flags, timestamps, and other non-personal data. This appears to be a WordPress links table with no user or contact information.
daily-signal_dev_database_new__wp_login_security_solution_fail.csv5 columns1,219,835 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 0 | skip | high | column 'fail_id' is an internal numeric ID |
| 1 | skip | high | column 'ip' contains internal network IPs, not public PII addresses |
| 2 | username | high | column 'user_login' contains login identifiers including '%firstuser%' placeholder and actual usernames like 'admin' and 'dailysignal' |
| 3 | password | high | column 'pass_md5' contains MD5 password hashes |
| 4 | skip | high | column 'date_failed' is a timestamp, not PII |
Notes: This is a WordPress login failure log table containing username attempts and password hashes. Only username and password hash columns contain PII. IP addresses are internal network IPs and timestamps are not PII.
daily-signal_dev_database_new__wp_mobilepress.csv0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
Notes: This is not a PII-containing file. The data appears to be WordPress options table entries showing version numbers, settings flags, and theme paths. No personal identifiers (emails, names, addresses, etc.) are present in the sample rows. All columns represent internal site configuration and are safe to skip.
daily-signal_dev_database_new__wp_options.csv3 columns0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 5 | skip | high | [5] header 'admin_email', values contain '@' and domain heritage.org |
| 41318 | password | medium | [41318] header 'auth_salt', values are cryptographic hashes/salts |
| 41361 | password | high | [41361] header 'ftp_credentials', contains username/password structure |
Notes: Identified 3 PII columns: admin email address and two password/salt fields. The dump contains WordPress options table with configuration data, credentials, and salts but no direct user names or other PII in the first 50 rows.
daily-signal_dev_database_new__wp_paramount_groups.csv0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
Notes: This is a structured CSV file with columns: id, groupname, groupid, smartlistid, suppressionid, dynamicid. None of these columns contain any PII data. They appear to be internal identifiers and group names for a mailing list or notification system. All columns map to skip categories (internal IDs or non-PII flags).
daily-signal_dev_database_new__wp_popularpostsdata.csv0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
Notes: The file contains only numeric IDs and date/timestamp values with pageview counts. No personal identifiable information (PII) is present in any column based on header names and sample values. All columns are internal analytics data (post IDs, view dates, and view counts) and should be skipped.
daily-signal_dev_database_new__wp_popularpostsdatacache.csv0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: no·Quote: "
Notes: This is a simple CSV containing only numeric IDs, dates, and pageview counts. No PII fields are present. All columns are internal analytics data and do not map to any PII categories.
daily-signal_dev_database_new__wp_postmeta.csv0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
Notes: This is a WordPress metadata table dump (wp_postmeta). All values are internal key-value pairs where meta_key values like '_edit_lock' and '_edit_last' are system-generated timestamps/user IDs, and meta_value contains lock timestamps or user IDs. No PII exists in this dataset. The file contains no email addresses, phone numbers, names, or other personal data.
daily-signal_dev_database_new__wp_posts.csv0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
Notes: No PII columns found. All columns are internal WordPress IDs, timestamps, content fields, status flags, and metadata. The post_author field contains numeric user IDs (not names or emails), and all other columns contain non-PII data such as post content, status flags, and technical metadata. No email addresses, phone numbers, names, addresses, DOB, SSN, passwords, or usernames are present.
daily-signal_dev_database_new__wp_redirection_404.csv5 columns0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 8 | skip | high | column 'referrer' contains URLs and tracking data, not PII |
| 9 | skip | high | column 'http_code' contains HTTP status codes, not PII |
| 10 | skip | high | column 'request_method' contains HTTP methods (GET, POST), not PII |
| 11 | skip | high | column 'request_data' contains request payloads, may contain PII but not reliably mappable |
| 12 | skip | high | column 'ip' contains IP addresses which are network identifiers, not physical addresses per exclusion rules |
Notes: This is a WordPress access log table tracking HTTP requests. Contains request metadata (URLs, user agents, HTTP codes) and IP addresses. No direct PII fields (names, emails, etc.) are present. IP addresses are excluded per rules as network identifiers.
daily-signal_dev_database_new__wp_redirection_items.csv0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
Notes: This is a WordPress redirect table (wp_redirection). No PII is present — columns contain redirect URLs, status codes, and timestamps. All values are technical configuration data, not personal information.
daily-signal_dev_database_new__wp_rg_form.csv0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
Notes: This is a simple table with four columns: id, title, date_created, is_active. There are no PII fields present. The data appears to be internal identifiers and flags, not containing any personal information such as email, phone, names, addresses, or other sensitive data. Therefore, no columns map to PII fields.
daily-signal_dev_database_new__wp_rg_form_meta.csv0 rows
File structure
Notes: This is a WordPress MySQL dump containing serialized PHP structures (a:37:{...}) and form configuration metadata. There are no actual user records or PII values in this sample row — it's purely schema/config data. The dump likely contains PII elsewhere in other tables (e.g., wp_users, wp_comments), but this specific file is unstructured configuration data with no extractable PII columns.
daily-signal_dev_database_new__wp_rg_form_view.csv0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
Notes: This is NOT a PII-containing file. The columns are purely internal tracking fields: id (internal record ID), form_id (Gravity Forms identifier), date_created (timestamp), ip (network identifier, excluded per rules), and count (counters). No personal names, addresses, emails, or other PII fields are present. The IP address is explicitly excluded from mapping per the exclusion rules for network identifiers.
daily-signal_dev_database_new__wp_sendfeed.csv2 columns0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 3 | medium | [3] header 'recipient', binary-encoded values decode to email addresses (e.g. 0x6D6174746865772E7370616C64... = 'matthew.spald...') | |
| 7 | medium | [7] header 'from_email', binary-encoded values decode to email addresses (e.g. 0x626C6F674068657269746167652... = 'blog@heritage...') |
Notes: WordPress RSS feed notification table (likely wp_rss_feed_email or similar plugin table). Most columns are binary-encoded blobs (feed names, URLs, templates, timestamps). Columns 3 and 7 contain binary-encoded email addresses. No other decodable PII fields present.
daily-signal_dev_database_new__wp_sendfeed_lock.csv1 rows
File structure
Notes: Unstructured fallback: no PII columns mapped, but the raw text carries emails
daily-signal_dev_database_new__wp_sendfeed_logs.csv0 rows
File structure
Notes: free-form text with embedded emails / phones
daily-signal_dev_database_new__wp_sticky.csv0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
Notes: This is a simple two-column table representing sticky post IDs and their status flags. Neither column contains PII. The data appears to be internal WordPress configuration for post prioritization and does not expose any user-identifiable information.
daily-signal_dev_database_new__wp_term_relationships.csv0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: no·Quote: "
Notes: This is a pure taxonomy relationship table (object_id, term_taxonomy_id, term_order) with no PII fields. All values are numeric IDs and ordering positions. No email addresses, names, or other personal data appear in the sample.
daily-signal_dev_database_new__wp_term_taxonomy.csv3,067 rows
File structure
Notes: Unstructured fallback: no PII columns mapped, but the raw text carries emails
daily-signal_dev_database_new__wp_terms.csv25 rows
File structure
Notes: Unstructured fallback: no PII columns mapped, but the raw text carries emails
daily-signal_dev_database_new__wp_usermeta.csv302 rows
File structure
Notes: Unstructured fallback: no PII columns mapped, but the raw text carries emails
daily-signal_dev_database_new__wp_users.csv4 columns3,006 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 1 | username | high | header "user_login" resolves to PII field "username" |
| 2 | password | high | header "user_pass" resolves to PII field "password" |
| 4 | high | header "user_email" resolves to PII field "email" | |
| 9 | fullName | high | header "display_name" resolves to PII field "fullName" |
Notes: Heuristic auto-detection: header-named PII columns confirmed by data conformance
daily-signal_dev_database_new__wp_yoast_indexable.csv0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
Notes: This is a WordPress MySQL database dump table (likely wp_seo_links or similar). All columns contain internal IDs, metadata, SEO settings, timestamps, and URLs. No PII fields (email, phone, name, address, DOB, SSN, etc.) are present. The 'title' and 'description' columns contain article headlines and excerpts, not personal data. Twitter and Open Graph image URLs point to Gravatar or content images, not personal identifiers.
daily-signal_dev_database_new__wp_yoast_indexable_hierarchy.csv0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: no·Quote: "
Notes: This is a pure hierarchy/relationship table with no PII fields. Columns are purely numeric IDs and tree depth counters. No email, name, address, or other personal data present.
daily-signal_dev_database_new__wp_yoast_migrations.csv0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
Notes: This is a simple two-column table with numeric IDs and version strings. No PII is present — these appear to be internal revision IDs and version timestamps. All columns are non-PII per exclusion rules (internal IDs and timestamps).
daily-signal_dev_database_new__wp_yoast_primary_term.csv0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
Notes: No PII columns identified. This appears to be a WordPress term_relationships table listing category associations with posts. Contains only numeric IDs (post_id, term_id), taxonomy names, and timestamps — none contain personal information.
daily-signal_dev_database_new__wp_yoast_seo_links.csv120,741 rows
File structure
Notes: Unstructured fallback: no PII columns mapped, but the raw text carries emails
daily-signal_dev_database_new__wp_yoast_seo_meta.csv0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: no·Quote: "
Notes: This is a raw WordPress MySQL dump table with no actual PII in the visible sample. The columns appear to be internal link counters and object IDs. No email, phone, name, address, or other PII fields are present in the first 50 rows. The data appears to be internal link relationship metrics (object_id, internal_link_count, incoming_link_count). No PII columns to map.