MAP context record

The Mosquito-Fighting Gear Worth Trying—and What to Skip

Source: https://www.wired.com/story/best-mosquito-repellents/ · About this source
Published: 2026-10-03
First observed: Oct 3, 2026 13:36 UTC
Last observed: Oct 3, 2026 13:36 UTC (1 observation)
Related MAP entity pages: No MAP entity page keyword appears in the headline

MAP could not extract this page's body or headline, so a frame below that says nothing was found is not a finding about the page.

The seven frames

Origin

This content is hosted on wired.com.

The current article identifies Christopher Null as the author, drawn from structured data on the page.

A publish date of 2026-10-03 was found in the page's metadata.

Attribution

The page contains 2 outbound links.

No structural attribution phrasing (e.g. "according to," "officials say") was detected in the headline or description. This reflects only the headline/description text — attribution may still be present in the body content, which this record does not deeply parse.

Specificity

No body content could be extracted from the page, so its level of detail could not be assessed.

Timing

No clear temporal framing could be identified in the headline or description.

This is a keyword-based structural proxy, not verb-tense or temporal-expression parsing.

Framing

The content follows a "standard article" presentation pattern.

The headline is structurally characterized as: moderate length, declarative, title case.

Context Change

MAP has one observation of this URL, so there is nothing to compare yet.

Information Relationships

2 outbound links were found in the content MAP extracted. MAP stores at most 10 referenced domains per record; 0 remain after removing the publisher's own site, social platforms and account or CDN hosts.

What MAP observed, check by check

For each frame, what MAP's automated extraction found on the page it read, one check at a time. “Not found” means the item was not in the page metadata or text MAP read; it does not show that the page, the publisher or the reporting lacks it. “Not read” means MAP could not check the item. Rows about MAP's own observations or filters use their own plain words where nothing was found. MAP does not score, rate or grade pages.

Show all checks

Origin

Publisher domain: Found — wired.com
Author or byline in the page metadata: Not read — MAP could not read this page, so this was not checked.
Publish date in the page metadata: Not read — MAP could not read this page, so this was not checked.

Attribution

Outbound links in the extracted content: Not read — MAP could not read this page, so this was not checked.
Attribution wording in the headline or description: Not read — MAP could not read this page, so this was not checked.

Specificity

Body text extracted: Not read — MAP could not read this page, so this was not checked.
Date-like references in the body text: Not read — MAP could not read this page, so this was not checked.

Timing

Past, present or future wording in the headline or description: Not read — MAP could not read this page, so this was not checked.

Framing

Presentation pattern: Not read — MAP could not read this page, so this was not checked.
Headline structure: Not read — MAP could not read this page, so this was not checked.

Context Change

Repeat observations of this URL: Once — MAP has observed this URL once, so there is nothing to compare yet.

Information Relationships

Referenced domains after MAP's filters: Not read — MAP could not read this page, so this was not checked.

What this record does not show

MAP could not read this page's headline or body, so it concludes nothing here about what the page does or does not show.

Outside the scope of a MAP record

Earlier events, votes, filings or contracts connected to the story. A MAP record does not look these up or link them to the story, and it does not judge what a story leaves out.
Coverage of the same event by other outlets. MAP does not compare coverage across outlets.
Later edits or corrections by the publisher, other than differences MAP happened to observe between its own repeat observations.
Who the people and organizations named on the page are. The name-like sequences in the Specificity frame are a structural proxy, not identified names.

See the Transparency Explanations page and the Methodology.

What changed

This URL has been observed once, so there is nothing to compare yet.

Other recent records from this source

www.wired.com/story/gift-cards-and-digital-gift-ideas/ (Oct 4, 2026)
www.wired.com/review/meta-glasses-gen-3/ (Oct 4, 2026)
www.wired.com/story/best-gifts-under-25-2026/ (Oct 4, 2026)
www.wired.com/story/keurig-alta-coffee-brewer/ (Oct 4, 2026)
www.wired.com/story/rural-data-centers-are-in-for-a-big-federal-tax-break/ (Oct 4, 2026)

Provenance

Record ID: 30fbdebb-d772-4456-a199-219bf4ce059e
This record observed: Oct 3, 2026 13:36 UTC
Ledger position: 27991
Record hash (SHA-256): a79a23d1972baf5fa0a0e6d01389b136440962e11cde152507b3e623e12b6138
Previous hash: 56870956be81c34fb2ca7550d8d86e02ce5da18ea15e5308035b68309c23e2bf
Link to previous entry: continuous

MAP operates this ledger. The hashes are published here for reference; MAP does not publish the data needed to recompute them.

Chain check (run Oct 4, 2026 10:00 UTC): 19,729 of 19,748 links between consecutive hashed entries are continuous (an entry's recorded previous hash equals the hash of the entry before it); 19 are not, and the ledger's position numbering has 3 gaps. MAP has not published the cause of each exception. 7,068 older rows have no hash. This checks continuity only; it does not recompute the hashes.

A record reflects the page as MAP fetched it at one moment. MAP does not determine whether content is true, false, biased, or trustworthy. MAP could not extract this page's body or headline, so a frame saying nothing was found is not a finding about the page. Methodology · JSON