Hostname
lumen.me
Last fetched
lumen.me resolves to 13.226.244.102, announced in 13.226.244.0/22 by AMAZON-02 - Amazon.com, Inc. in DE. lumen.me 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.226.244.102
13.226.244.0/22 · AMAZON-02 - Amazon.com, Inc. · Frankfurt am Main, DE
- 13.226.244.124
13.226.244.0/22 · AMAZON-02 - Amazon.com, Inc. · Frankfurt am Main, DE
- 13.226.244.52
13.226.244.0/22 · AMAZON-02 - Amazon.com, Inc. · Frankfurt am Main, DE
- 13.226.244.84
13.226.244.0/22 · AMAZON-02 - Amazon.com, Inc. · Frankfurt am Main, DE
- 13.227.192.37
13.227.192.0/24 · AMAZON-02 - Amazon.com, Inc. · Prague, CZ
- 13.227.192.47
13.227.192.0/24 · AMAZON-02 - Amazon.com, Inc. · Prague, CZ
- 13.227.192.66
13.227.192.0/24 · AMAZON-02 - Amazon.com, Inc. · Prague, CZ
- 13.227.192.72
13.227.192.0/24 · AMAZON-02 - Amazon.com, Inc. · Prague, CZ
- 18.215.9.104
18.208.0.0/13 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 18.239.18.108
18.239.16.0/21 · AMAZON-02 - Amazon.com, Inc. · Amsterdam, NL
- 18.239.18.116
18.239.16.0/21 · AMAZON-02 - Amazon.com, Inc. · Amsterdam, NL
- 18.239.18.49
18.239.16.0/21 · AMAZON-02 - Amazon.com, Inc. · Amsterdam, NL
- 18.239.18.92
18.239.16.0/21 · AMAZON-02 - Amazon.com, Inc. · Amsterdam, NL
- 3.160.39.128
3.160.36.0/22 · AMAZON-02 - Amazon.com, Inc. · Berlin, DE
- 3.160.39.47
3.160.36.0/22 · AMAZON-02 - Amazon.com, Inc. · Berlin, DE
- 3.160.39.57
3.160.36.0/22 · AMAZON-02 - Amazon.com, Inc. · Berlin, DE
- 3.160.39.67
3.160.36.0/22 · AMAZON-02 - Amazon.com, Inc. · Berlin, DE
- 3.217.26.76
3.208.0.0/12 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 3.231.255.103
3.224.0.0/12 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 3.81.247.159
3.80.0.0/12 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
IPv6 resolution
No AAAA record for lumen.me is recorded in WhisperGraph.
Attribution
Aws
cloud · ORIGIN_AS
WHOIS identity
- Registrar
- iana:146
- Registrant organisation
- domains by proxy,
Subdomains
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
- ns-347.awsdns-43.com
- ns-770.awsdns-32.net
- ns-1194.awsdns-21.org
- ns-1724.awsdns-23.co.uk
MX records
- aspmx.l.google.com
- alt1.aspmx.l.google.com
- alt2.aspmx.l.google.com
- aspmx2.googlemail.com
- aspmx3.googlemail.com
SPF policy
- include: _spf.google.com
- include: spf.mandrillapp.com
- include: _spf.salesforce.com
- include: shops.shopify.com
- a: lumen.me
- mx: lumen.me
- include: servers.mcsv.net
Threat-feed evidence
History
Related pages
Pivot from lumen.me 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: "lumen.me"})-[: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.