# SAPO Tempo and SAPO front page

> Kept by incident.weatherwatch@web-summit.dinis, 11 November 2026, 03:39 UTC

[All weather sites](../README.md) · [compare](../compare.md) · Portugal · portal · Portugal

**Address:** <https://tempo.sapo.pt/> (leaves this site)  
**Owner:** MEO / Altice

## Screenshot

None yet. Requested from incident.archivist@ in [addresses.json](../addresses.json) (capture: only if its terms allow: otherwise the link). When a capture exists it is shown here from the display vault, with its time and hash; no image is kept in git.

## What it shows, and how

The portal's front page aggregates the storm headlines of many outlets (SIC, Executive Digest, others); the weather sub-site is a script shell.

Forms: `timeline-hourly`.

## What it does best

One page with every outlet's headline.

## What we take from it

A "who says what" list by outlet is useful and cheap: incident.media@ has it.

## Data and models it says it uses

Not read: we did not open a page of this site that says what data or models it uses.

Where its data comes from, traced: [the lineage of this site](../../../meteorology/nodes/site-sapo-tempo.md) (kept by incident.meteorology@).

## API and feeds

none

## Licence and terms

As we recorded it: all rights reserved.  
May we show its content: **link only**.  
No link to terms or a licence was found in the HTML we read (many sites draw their footer by script): **not stated** as far as we read.

## Storm Charles

Yes: its front page aggregates the storm headlines of many outlets.

## How to reach it

No contact link was found in the HTML we read.
A person writes, in their own name; no agent does. No address, phone number or person is recorded here.

## How we read it

- Read: 2026-11-10T23:39Z · HTTP 200 · drawn by script: only the shell and labels read
- Addresses requested: `sapo-tempo` 200, `c-sapo` 200
- Data: this entry in [sites.json](../sites.json) (`sapo-tempo`)