Hostname
pressreader.com
Last fetched
pressreader.com resolves to 2 IPv4 addresses operated by CLOUDFLARENET - Cloudflare, Inc. in CA. WHOIS lists iana:321 as the registrar.
Nutrition Label
Resolution chain
pressreader.com resolves to 2 distinct IPv4 addresses via WhisperGraph DNS data. Each row links to the IP, prefix, and announcing ASN.
| IP | Prefix | ASN | Operator | Country |
|---|---|---|---|---|
| 104.18.230.240 | 104.18.224.0/20 | AS13335 | CLOUDFLARENET - Cloudflare, Inc. | CA |
| 104.18.231.240 | 104.18.224.0/20 | AS13335 | CLOUDFLARENET - Cloudflare, Inc. | CA |
WHOIS identity
- Registrar
- iana:321
- Organization
- newspaperdirect
- Contact emails
Subdomains
337 observed subdomains of pressreader.com.
Showing 25 of 337. View all subdomains →
Web-graph footprint
Distinct hostnames that link to or from pressreader.com in the public web crawl.
21,578 sites link to this hostname.
Threat posture
History
Mail and authentication
SPF policy
17 SPF mechanisms authorising senders for pressreader.com.
| Mechanism | Target |
|---|---|
| SPF_INCLUDE | 5357741.spf07.hubspotemail.net |
| SPF_INCLUDE | amazonses.com |
| SPF_INCLUDE | mail.zendesk.com |
| SPF_INCLUDE | sendgrid.net |
| SPF_INCLUDE | servers.mcsv.net |
| SPF_INCLUDE | spf-007eaf01.pphosted.com |
| SPF_INCLUDE | spf.protection.outlook.com |
| SPF_IP | 204.50.102.246 |
| SPF_IP | 204.50.102.29 |
| SPF_IP | 204.50.102.44 |
| SPF_IP | 208.181.59.23 |
| SPF_IP | 208.181.59.246 |
| SPF_IP | 208.181.59.253 |
| SPF_IP | 208.181.59.34 |
| SPF_IP | 208.181.59.36 |
| SPF_IP | 208.181.59.39 |
| SPF_MX | pressreader.com |
Related pages
Pivot deeper into the graph from pressreader.com.
- IP · 104.18.230.240
- ASN · AS13335CLOUDFLARENET - Cloudflare, Inc.
- Registrar · iana:321
- Country · CA
- Email · nospam-11920@rtwhoisenvoy.net
- TLD · .com
- Browse hostnames · pr…
- Glossary · What is a hostname?
- Whisper Internet Directory — home
- Live MOAS conflicts feed
- Threat feed · Spamhaus DROP
- United States internet infrastructure
Cypher and MCP
Reproduce the resolution chain directly against graph.whisper.security:
MATCH (h:HOSTNAME {name: "pressreader.com"})-[:RESOLVES_TO]->(ip:IPV4)
-[:ANNOUNCED_BY]->(ap:ANNOUNCED_PREFIX)
-[:ROUTES]->(asn:ASN)-[:HAS_NAME]->(n:ASN_NAME)
RETURN ip.name AS ip, ap.name AS prefix, asn.name AS asn, n.name AS operator
LIMIT 20Or query Whisper from your own LLM workflow via the Whisper MCP server.