Hostname
harmo.me
Last fetched
harmo.me resolves to 13.35.37.122, announced in 13.35.37.0/24 by AMAZON-02 - Amazon.com, Inc. in SG. harmo.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.35.37.122
13.35.37.0/24 · AMAZON-02 - Amazon.com, Inc. · Singapore, SG
- 13.35.37.19
13.35.37.0/24 · AMAZON-02 - Amazon.com, Inc. · Singapore, SG
- 13.35.37.62
13.35.37.0/24 · AMAZON-02 - Amazon.com, Inc. · Singapore, SG
- 13.35.37.77
13.35.37.0/24 · AMAZON-02 - Amazon.com, Inc. · Singapore, SG
- 18.173.166.13
18.173.166.0/23 · AMAZON-02 - Amazon.com, Inc. · Miami, US
- 18.173.166.52
18.173.166.0/23 · AMAZON-02 - Amazon.com, Inc. · Miami, US
- 18.173.166.55
18.173.166.0/23 · AMAZON-02 - Amazon.com, Inc. · Miami, US
- 18.173.166.74
18.173.166.0/23 · AMAZON-02 - Amazon.com, Inc. · Miami, US
- 3.217.84.88
3.208.0.0/12 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 3.219.144.155
3.208.0.0/12 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 3.225.214.105
3.224.0.0/12 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 3.226.182.201
3.224.0.0/12 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 34.193.249.197
34.192.0.0/12 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 34.202.180.181
34.192.0.0/12 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 34.202.41.15
34.192.0.0/12 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 44.219.37.194
44.192.0.0/11 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 52.4.174.39
52.4.0.0/14 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 98.85.10.80
98.80.0.0/13 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 99.84.152.121
99.84.152.0/21 · AMAZON-02 - Amazon.com, Inc. · Frankfurt am Main, DE
- 99.84.152.129
99.84.152.0/21 · AMAZON-02 - Amazon.com, Inc. · Frankfurt am Main, DE
IPv6 resolution
No AAAA record for harmo.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-110.awsdns-13.com
- ns-934.awsdns-52.net
- a.root-servers.net
- b.root-servers.net
- c.root-servers.net
- d.root-servers.net
- e.root-servers.net
- f.root-servers.net
- g.root-servers.net
- h.root-servers.net
- i.root-servers.net
- j.root-servers.net
- k.root-servers.net
- l.root-servers.net
- m.root-servers.net
- ns-1457.awsdns-54.org
- ns-1948.awsdns-51.co.uk
MX records
- aspmx.l.google.com
- alt1.aspmx.l.google.com
- alt2.aspmx.l.google.com
- alt3.aspmx.l.google.com
- alt4.aspmx.l.google.com
SPF policy
- include: amazonses.com
- include: _spf.google.com
- include: spf.ecentry.io
- a: harmo.me
- mx: harmo.me
- include: 21109177.spf01.hubspotemail.net
- include: sendgrid.net
Threat-feed evidence
History
Related pages
Pivot from harmo.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: "harmo.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.