Hostname
rolex.org
Last fetched
rolex.org resolves to 2.16.241.206, announced in 2.16.241.0/24 by AKAMAI-ASN1 - Akamai International B.V. in DE. rolex.org 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
- 2.16.241.206
2.16.241.0/24 · AKAMAI-ASN1 - Akamai International B.V. · Frankfurt am Main, DE
- 2.16.241.227
2.16.241.0/24 · AKAMAI-ASN1 - Akamai International B.V. · Frankfurt am Main, DE
- 23.222.236.158
23.222.236.0/24 · AKAMAI-ASN1 - Akamai International B.V. · Chicago, US
- 23.222.236.187
23.222.236.0/24 · AKAMAI-ASN1 - Akamai International B.V. · Chicago, US
- 23.33.40.133
23.33.40.0/24 · AKAMAI-ASN1 - Akamai International B.V. · New York, US
- 23.33.40.151
23.33.40.0/24 · AKAMAI-ASN1 - Akamai International B.V. · New York, US
- 23.44.131.212
23.44.131.0/24 · AKAMAI-ASN1 - Akamai International B.V. · New York, US
- 23.44.131.213
23.44.131.0/24 · AKAMAI-ASN1 - Akamai International B.V. · New York, US
- 23.53.1.150
23.53.1.0/24 · AKAMAI-ASN1 - Akamai International B.V. · Marseille, FR
- 23.53.1.151
23.53.1.0/24 · AKAMAI-ASN1 - Akamai International B.V. · Marseille, FR
- 95.101.234.85
95.101.234.0/24 · AKAMAI-ASN1 - Akamai International B.V. · Marseille, FR
- 95.101.234.87
95.101.234.0/24 · AKAMAI-ASN1 - Akamai International B.V. · Marseille, FR
IPv6 resolution
No AAAA record for rolex.org is recorded in WhisperGraph.
Attribution
akamai international
ORIGIN_AS
WHOIS identity
Subdomains
Showing 5 of 5 subdomains (5 per page).
Web-graph footprint
Sampled `LINKS_TO` edges. The hyperlink layer is a pilot sample, not a web-scale crawl, so these are illustrative.
Sample inbound links
Mail and authentication
Nameservers
- dns1.p02.nsone.net
- dns2.p02.nsone.net
- dns3.p02.nsone.net
- dns4.p02.nsone.net
Threat-feed evidence
History
Related pages
Pivot from rolex.org 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: "rolex.org"})-[: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.