Hostname
documentreader.cc
Last fetched
documentreader.cc resolves to 13.227.192.104, announced in 13.227.192.0/24 by AMAZON-02 - Amazon.com, Inc. in CZ. documentreader.cc is not listed on any threat feed indexed by WhisperGraph; reconciled level NONE.
Threat posture
0threat score (procedure-native scale)
NONENo threats observed.
- Threat feeds listing this
- 0
- Verdict coverage
- known-clean
Nutrition Label
Resolution chain
- 13.227.192.104
13.227.192.0/24 · AMAZON-02 - Amazon.com, Inc. · Prague, CZ
- 13.227.192.111
13.227.192.0/24 · AMAZON-02 - Amazon.com, Inc. · Prague, CZ
- 13.227.192.25
13.227.192.0/24 · AMAZON-02 - Amazon.com, Inc. · Prague, CZ
- 13.227.192.61
13.227.192.0/24 · AMAZON-02 - Amazon.com, Inc. · Prague, CZ
- 18.64.119.12
18.64.112.0/21 · AMAZON-02 - Amazon.com, Inc. · Dublin, IE
- 18.64.119.19
18.64.112.0/21 · AMAZON-02 - Amazon.com, Inc. · Dublin, IE
- 18.64.119.28
18.64.112.0/21 · AMAZON-02 - Amazon.com, Inc. · Dublin, IE
- 18.64.119.63
18.64.112.0/21 · AMAZON-02 - Amazon.com, Inc. · Dublin, IE
- 18.66.248.102
18.66.248.0/22 · AMAZON-02 - Amazon.com, Inc. · Düsseldorf, DE
- 18.66.248.125
18.66.248.0/22 · AMAZON-02 - Amazon.com, Inc. · Düsseldorf, DE
- 18.66.248.49
18.66.248.0/22 · AMAZON-02 - Amazon.com, Inc. · Düsseldorf, DE
- 18.66.248.63
18.66.248.0/22 · AMAZON-02 - Amazon.com, Inc. · Düsseldorf, DE
- 3.162.125.21
- 3.162.125.60
- 3.162.125.63
- 3.162.125.8
IPv6 resolution
No AAAA record for documentreader.cc is recorded in WhisperGraph.
Attribution
Aws
cloud · ORIGIN_AS
WHOIS identity
WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for documentreader.cc. WHOIS is recorded against the registrable domain, so a subdomain such as a www. host carries none of its own — check the registrable domain for this name.
Subdomains
Mail and authentication
Nameservers
- ns-295.awsdns-36.com
- ns-967.awsdns-56.net
- ns-1237.awsdns-26.org
- ns-1946.awsdns-51.co.uk
Threat-feed evidence
History
Related pages
Pivot from documentreader.cc into the addresses, networks and registries it depends on.
Cypher and MCP
Reproduce this hostname's resolution chain against graph.whisper.security:
MATCH (h:HOSTNAME {name: "documentreader.cc"})-[:RESOLVES_TO]->(ip:IPV4)
-[:ANNOUNCED_BY]->(ap:ANNOUNCED_PREFIX)-[:ROUTES]->(a:ASN)
OPTIONAL MATCH (a)-[:HAS_NAME]->(n:ASN_NAME)
RETURN ip.name AS ip, ap.name AS prefix, a.name AS asn, n.name AS network
LIMIT 20Or query Whisper from your own LLM workflow via the Whisper MCP server.